Optimization of encoding cycles for object recovery feed

ABSTRACT

The disclosed embodiments relate generally to efficient data encoding and transmission. An encoding system determines an encoding interval at which to encode different groups of related data in a data structure. The encoding interval for each group encoded together optimizes the amount of newly received information that is encoded and transmitted in a continuous, repeating loop.

REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit as a continuation of U.S. patent application Ser. No. 17/007,905, filed Aug. 31, 2020, entitled, “OPTIMIZATION OF ENCODING CYCLES FOR OBJECT RECOVERY FEED”, now U.S. Pat. No. ______, issued ______, which claims priority to and the benefit as a continuation of U.S. patent application Ser. No. 15/383,477, filed Dec. 19, 2016, entitled, “OPTIMIZATION OF ENCODING CYCLES FOR OBJECT RECOVERY FEED”, now U.S. Pat. No. 10,812,613, issued Oct. 20, 2020, the entirety of which are incorporated by reference herein and relied upon.

BACKGROUND

A data transaction processing system receives instructions or requests to perform transactions. The result of performing transactions may be a modification in the state of an object. The data transaction processing system then reports, or publishes, the results of the performed transactions, or the state of the object, to a plurality of data recipient systems.

Each data recipient system maintains its own version of the object, and receives incremental changes to the state of the object from the data transaction processing system. The data recipient system updates its local copy of the state of the object based on the incremental data feed.

The data transaction processing system also publishes a snapshot of the current state of the object that can be used by the data recipient system to perform object recovery, e.g., regain the current state of the object, in case of data recipient system failure. The snapshot is also updated as new incremental changes are generated by the data transaction processing system. The snapshot is encoded, e.g., into Simple Binary Encoding, which is used for high throughput, low latency data transmission, and published via a snapshot feed to data recipient computing systems. If the data transaction processing system generates many incremental changes, the snapshot that is published to the data recipient system may not be accurate, or may not be timely published to the data recipient system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an illustrative computer network system that may be used to implement aspects of the disclosed embodiments.

FIG. 2 depicts an illustrative embodiment of a general computer system for use with the disclosed embodiments.

FIG. 3 depicts an example market order message management system for implementing the disclosed embodiments.

FIG. 4A depicts an illustrative embodiment of a data structure used to implement aspects of the disclosed embodiments.

FIG. 4B depicts an illustrative embodiment of an alternative data structure used to implement aspects of the disclosed embodiments.

FIG. 4C depicts an illustrative embodiment of order book data structures holding example messages used to implement aspects of the disclosed embodiments.

FIG. 5 illustrates an example data structure diagram of inbound and outbound messages used to implement aspects of the disclosed embodiments.

FIG. 6A illustrates an example Per Order object message.

FIG. 6B illustrates an example Aggregated by Value object message.

FIG. 7 illustrates an exchange computing system and a data recipient computing system configured to perform object recovery implementing aspects of the disclosed embodiments.

FIG. 8 illustrates a block diagram of an example snapshot adaptor used to implement aspects of the disclosed embodiments.

FIG. 9 illustrates example process pipelines executed by a snapshot adaptor to implement aspects of the disclosed embodiments.

FIG. 10 illustrates an example state diagram for an instrument cache according to the disclosed embodiments.

FIG. 11 illustrates example experimental data associated with a snapshot adaptor.

FIG. 12 illustrates an example flowchart for implementing an example exchange computing system in accordance with the disclosed embodiments.

DETAILED DESCRIPTION

The disclosed embodiments relate generally to efficient data encoding and transmission. Specifically, the disclosed embodiments provide systems and methods for optimizing when a snapshot of an object that is frequently updated (e.g., continually refreshed) should be encoded and transmitted, minimizing any transmission delay while transmitting as much encoded information as possible. The snapshot data may be encoded into a format useful for low latency publishing or transmission, and in a format expected by a data recipient computing system. For example, the disclosed encoding system may encode data into a SBE (Simple Binary Encoding) format, a protocol supporting applications requiring extremely low latency.

A data transaction processing system may, in one embodiment, continuously process incoming requests to perform transactions, and report the results of performing, or attempting to perform, the transactions, including modification of a data object representing a state of the computing environment. The data transaction processing system may also provide a snapshot of the object that can be consumed by data recipient systems for recovery purposes. The snapshot is made readily available so that if the data recipient system loses its connection with the data transaction processing system, the data recipient system can quickly recover the state of the object as quickly as possible, and recover as close to the current state of the object as possible.

The disclosed encoding system, in one embodiment, uses historical data about the various financial instruments within an order book data object to determine when the snapshot should be encoded and prepared for transmission. As the size of the data object fluctuates and varies, the encoding system dynamically updates or modifies the encoding intervals for the different instruments within a snapshot to optimize the amount of new information encoded and transmitted via a continuous loop provided to the data recipient system. Thus, for a same given instrument cache, the encoding interval may vary at different times. An instrument cache may be encoded at a first encoding interval, and then the next time it is encoded, be encoded at a second, different encoding interval, due to the changing sizes of the instrument caches and/or the contents of the transmission buffer.

The data transaction processing system, may, in one embodiment, operate in a stateful manner, i.e., depend upon historical/prior messages received, and/or rely upon previous results thereof or previous decisions made, by the transaction processing system. The data transaction processing system may also access data structures storing information about a current environment state to optimize and/or eliminate encoding cycles.

The disclosed embodiments improve upon the technical field of data processing, in one embodiment, by eliminating unnecessary encoding cycles of a snapshot that is useful for object recovery. In a system where the snapshot includes many records for many instruments, and all of the records for an instrument are encoded together, optimizing and eliminating encoding cycles greatly reduces the processing burden on an encoding system, increasing overall computing efficiency.

The disclosed system is a specific implementation and practical application that allows the encoding system to dynamically determine exactly how much time or processing cycles should elapse before an instrument, including all of its entries, should be encoded and prepared for transmission. Moreover, encoded portions of the snapshot may be transmitted or published out continuously over a snapshot loop.

The disclosed encoding system improves upon the technical field of data processing and facilitating efficient object recovery by increasing the amount of renewed information that is encoded and transmitted, reducing the total number of messages transmitted, thus reducing the overall volume of data being communicated and the resources necessary in support thereof. The disclosed encoding system also makes efficient use of an encoding system by avoiding redundant data encoding by the encoding system in the particular environment of an object state which is highly dynamic and requires a substantial amount of time to encode, wherein the time to encode and publish a given object state likely substantially exceeds the frequency with which the object state is being updated.

The disclosed embodiments are directed to lessening the computational load of an object recovery process, while communicating as much of the new information as possible over a replication loop or feed.

At least some of the problems solved by the disclosed encoding system are specifically rooted in technology, specifically in data communications where data received from one process's output (e.g., a hardware matching process) is applied to modify portions of a snapshot that fluctuates in size and where the snapshot is partially encoded and transmitted for consumption by another independently acting process (e.g., an object recovery process), and are solved by means of a technical solution, namely, determining, or approximating, time intervals between encoding groups of related entries to optimize the amount of new data from the encoding process that is available for transmission over a replication feed to the object recovery process. For example, the disclosed embodiments relate to generating data and dynamically optimizing the amount of data that is encoded together so that the encoding process ends as the replication feed bandwidth becomes available. The disclosed embodiments solve a communications network-centric problem of sending large amount of related data sets that are independently received, encoded, and transmitted, and in particular, modify how communications are transmitted in order to solve a transmission problem.

Accordingly, the resulting problem is a problem arising in computer systems due to the high volume of disparate messages processed by an exchange computing system and made available for data object recovery e.g., if a client computer's primary copy of the object is lost or destroyed. The encoding system technology attempts to improve processing times by optimizing, and in some cases eliminating, encoding cycles by determining whether an encoding condition for a specific subset of data, e.g., a per-instrument encoding interval, has occurred. Each instrument, or different groups or subsets of related data, may be associated with its own encode process that is performed at its specific encoding interval. The method, in one embodiment, reduces the amount of times data is encoded. The solutions disclosed herein are, in one embodiment, implemented as automatic responses and actions by an exchange computing system computer.

The disclosed embodiments may be directed to an exchange computing system that includes multiple hardware matching processors that match, or attempt to match, electronic data transaction request messages with other electronic data transaction request messages counter thereto. Input electronic data transaction request messages may be received from different client computers over a data communication network, and output electronic data transaction result messages may be transmitted to the client computers and may be indicative of results of the attempts to match incoming electronic data transaction request messages. Orderer components and decider components implemented between the client computers and hardware matching processors shape and optimize the data flow.

The disclosed embodiments may be implemented in a data transaction processing system that processes data items or objects. Customer or user devices (e.g., computers) may submit electronic data transaction request messages, e.g., inbound messages, to the data transaction processing system over a data communication network. The electronic data transaction request messages may include, for example, transaction matching parameters, such as instructions and/or values, for processing the data transaction request messages within the data transaction processing system. The instructions may be to perform transactions, e.g., buy or sell a quantity of a product at a given value. Products, e.g., financial instruments, or order books representing the state of an electronic marketplace for a product, may be represented as data objects within the exchange computing system. The instructions may also be conditional, e.g., buy or sell a quantity of a product at a given value if a trade for the product is executed at some other reference value. The data transaction processing system may include various specifically configured matching processors that match, e.g., automatically, electronic data transaction request messages for the same one of the data items. The specifically configured matching processors may match electronic data transaction request messages based on multiple transaction matching parameters from the different client computers. The specifically configured matching processors may additionally generate information indicative of a state of an environment (e.g., the state of the order book) based on the processing, and report this information to data recipient computing systems via outbound messages published via one or more data feeds.

For example, one exemplary environment where efficient data object recovery is desirable is in financial markets, and in particular, electronic financial exchanges, such as a futures exchange, such as the Chicago Mercantile Exchange Inc. (CME).

A financial instrument trading system, such as a futures exchange, such as the Chicago Mercantile Exchange Inc. (CME), provides a contract market where financial instruments, e.g., futures and options on futures, are traded using electronic systems. “Futures” is a term used to designate all contracts for the purchase or sale of financial instruments or physical commodities for future delivery or cash settlement on a commodity futures exchange. A futures contract is a legally binding agreement to buy or sell a commodity at a specified price at a predetermined future time. An option contract is the right, but not the obligation, to sell or buy the underlying instrument (in this case, a futures contract) at a specified price within a specified time. The commodity to be delivered in fulfillment of the contract, or alternatively the commodity for which the cash market price shall determine the final settlement price of the futures contract, is known as the contract's underlying reference or “underlier.” The terms and conditions of each futures contract are standardized as to the specification of the contract's underlying reference commodity, the quality of such commodity, quantity, delivery date, and means of contract settlement. Cash settlement is a method of settling a futures contract whereby the parties effect final settlement when the contract expires by paying/receiving the loss/gain related to the contract in cash, rather than by effecting physical sale and purchase of the underlying reference commodity at a price determined by the futures contract, price. Options and futures may be based on more generalized market indicators, such as stock indices, interest rates, futures contracts and other derivatives.

An exchange may provide for a centralized “clearing house” through which trades made must be confirmed, matched, and settled each day until offset or delivered. The clearing house may be an adjunct to an exchange, and may be an operating division of an exchange, which is responsible for settling trading accounts, clearing trades, collecting and maintaining performance bond funds, regulating delivery, and reporting trading data. One of the roles of the clearing house is to mitigate credit risk. Clearing is the procedure through which the clearing house becomes buyer to each seller of a futures contract, and seller to each buyer, also referred to as a novation, and assumes responsibility for protecting buyers and sellers from financial loss due to breach of contract, by assuring performance on each contract. A clearing member is a firm qualified to clear trades through the clearing house.

An exchange computing system may operate under a central counterparty model, where the exchange acts as an intermediary between market participants for the transaction of financial instruments. In particular, the exchange computing system novates itself into the transactions between the market participants, i.e., splits a given transaction between the parties into two separate transactions where the exchange computing system substitutes itself as the counterparty to each of the parties for that part of the transaction, sometimes referred to as a novation. In this way, the exchange computing system acts as a guarantor and central counterparty and there is no need for the market participants to disclose their identities to each other, or subject themselves to credit or other investigations by a potential counterparty. For example, the exchange computing system insulates one market participant from the default by another market participant. Market participants need only meet the requirements of the exchange computing system. Anonymity among the market participants encourages a more liquid market environment as there are lower barriers to participation. The exchange computing system can accordingly offer benefits such as centralized and anonymous matching and clearing.

A match engine within a financial instrument trading system may comprise a transaction processing system that processes a high volume, e.g., millions, of messages or orders in one day. The messages are typically submitted from market participant computers. Exchange match engine systems may be subject to variable messaging loads due to variable market messaging activity. Performance of a match engine depends to a certain extent on the magnitude of the messaging load and the work needed to process that message at any given time. An exchange match engine may process large numbers of messages during times of high volume messaging activity. With limited processing capacity, high messaging volumes may increase the response time or latency experienced by market participants.

The disclosed embodiments recognize that electronic messages such as incoming messages from market participants, i.e., “outright” messages, e.g., trade order messages, etc., are sent from client devices associated with market participants, or their representatives, to an electronic trading or market system. For example, a market participant may submit an electronic message to the electronic trading system that includes an associated specific action to be undertaken by the electronic trading system, such as entering a new trade order into the market or modifying an existing order in the market. In one embodiment, if a participant wishes to modify a previously sent request, e.g., a prior order which has not yet been processed or traded, they may send a request message comprising a request to modify the prior request.

As used herein, a financial message, or an electronic message, refers both to messages communicated by market participants to an electronic trading or market system and vice versa. The messages may be communicated using packeting or other techniques operable to communicate information between systems and system components. Some messages may be associated with actions to be taken in the electronic trading or market system.

Financial messages communicated to the electronic trading system, also referred to as “inbound” messages, may include associated actions that characterize the messages, such as trader orders, order modifications, order cancelations and the like, as well as other message types. Inbound messages may be sent from market participants, or their representatives, e.g., trade order messages, etc., to an electronic trading or market system. For example, a market participant may submit an electronic message to the electronic trading system that includes an associated specific action to be undertaken by the electronic trading system, such as entering a new trade order into the market or modifying an existing order in the market. In one exemplary embodiment, the incoming request itself, e.g., the inbound order entry, may be referred to as an iLink message. iLink is a bidirectional communications/message protocol/message format implemented by the Chicago Mercantile Exchange Inc.

Financial messages communicated from the electronic trading system, referred to as “outbound” messages, may include messages responsive to inbound messages, such as confirmation messages, or other messages such as market update messages, quote messages, and the like. Outbound messages may be disseminated via data feeds.

Financial messages may further be categorized as having or reflecting an impact on a market or electronic marketplace, also referred to as an “order book” or “book,” for a traded product, such as a prevailing price therefore, number of resting orders at various price levels and quantities thereof, etc., or not having or reflecting an impact on a market or a subset or portion thereof. In one embodiment, an electronic order book may be understood to be an electronic collection of the outstanding or resting orders for a financial instrument.

For example, a request to place a trade may result in a response indicative of the trade either being matched with, or being rested on an order book to await, a suitable counter-order. This response may include a message directed solely to the trader who submitted the order to acknowledge receipt of the order and report whether it was matched, and the extent thereto, or rested. The response may further include a message to all market participants reporting a change in the order book due to the order. This response may take the form of a report of the specific change to the order book, e.g., an order for quantity X at price Y was added to the book (referred to, in one embodiment, as a Market By Order message), or may simply report the result, e.g., price level Y now has orders for a total quantity of Z (where Z is the sum of the previous resting quantity plus quantity X of the new order). In some cases, requests may elicit a non-impacting response, such as temporally proximate to the receipt of the request, and then cause a separate market-impact reflecting response at a later time. For example, a stop order, fill or kill order, also known as an immediate or cancel order, or other conditional request may not have an immediate market impacting effect, if at all, until the requisite conditions are met.

An acknowledgement or confirmation of receipt, e.g., a non-market impacting communication, may be sent to the trader simply confirming that the order was received. Upon the conditions being met and a market impacting result thereof occurring, a market-impacting message may be transmitted as described herein both directly back to the submitting market participant and to all market participants (in a Market By Price “MBP” e.g., Aggregated By Value (“ABV”) book, or Market By Order “MBO”, e.g., Per Order (“PO”) book format). It should be appreciated that additional conditions may be specified, such as a time or price limit, which may cause the order to be dropped or otherwise canceled and that such an event may result in another non-market-impacting communication instead. In some implementations, market impacting communications may be communicated separately from non-market impacting communications, such as via a separate communications channel or feed.

It should be further appreciated that various types of market data feeds may be provided which reflect different markets or aspects thereof. Market participants may then, for example, subscribe to receive those feeds of interest to them. For example, data recipient computing systems may choose to receive one or more different feeds. As market impacting communications usually tend to be more important to market participants than non-impacting communications, this separation may reduce congestion and/or noise among those communications having or reflecting an impact on a market or portion thereof. Furthermore, a particular market data feed may only communicate information related to the top buy/sell prices for a particular product, referred to as “top of book” feed, e.g., only changes to the top 10 price levels are communicated. Such limitations may be implemented to reduce consumption of bandwidth and message generation resources. In this case, while a request message may be considered market-impacting if it affects a price level other than the top buy/sell prices, it will not result in a message being sent to the market participants.

Examples of the various types of market data feeds which may be provided by electronic trading systems, such as the CME, in order to provide different types or subsets of market information or to provide such information in different formats include Market By Order or Per Order, Market Depth (also known as Market by Price or Aggregated By Value to a designated depth of the book), e.g., CME offers a 10-deep market by price feed, Top of Book (a single depth Market by Price feed), and combinations thereof. There may also be all manner of specialized feeds in terms of the content, i.e., providing, for example, derived data, such as a calculated index.

Market data feeds may be characterized as providing a “view” or “overview” of a given market, an aggregation or a portion thereof or changes thereto. For example, a market data feed, such as a Market By Price (“MBP”) feed, also known as an Aggregated By Value (“ABV”) feed, may convey, with each message, the entire/current state of a market, or portion thereof, for a particular product as a result of one or more market impacting events. For example, an MBP message may convey a total quantity of resting buy/sell orders at a particular price level in response to a new order being placed at that price. An MBP message may convey a quantity of an instrument which was traded in response to an incoming order being matched with one or more resting orders. MBP messages may only be generated for events affecting a portion of a market, e.g., only the top 10 resting buy/sell orders and, thereby, only provide a view of that portion. As used herein, a market impacting request may be said to impact the “view” of the market as presented via the market data feed.

An MBP feed may utilize different message formats for conveying different types of market impacting events. For example, when a new order is rested on the order book, an MBP message may reflect the current state of the price level to which the order was added, e.g., the new aggregate quantity and the new aggregate number of resting orders. As can be seen, such a message conveys no information about the resting orders, including the newly rested order, themselves to the market participants. Only the submitting market participant, who receives a separate private message acknowledging the event, knows that it was their order that was added to the book. Similarly, when a trade occurs, an MBP message may be sent which conveys the price at which the instrument was traded, the quantity traded and the number of participating orders, but may convey no information as to whose particular orders contributed to the trade. MBP feeds may further batch reporting of multiple events, i.e., report the result of multiple market impacting events in a single message.

Alternatively, a market data feed, referred to as a Market By Order (“MBO”) feed also known as a Per Order (“PO”) feed, may convey data reflecting a change that occurred to the order book rather than the result of that change, e.g., that order ABC for quantity X was added to price level Y or that order ABC and order XYZ traded a quantity X at a price Y. In this case, the MBO message identifies only the change that occurred so a market participant wishing to know the current state of the order book must maintain their own copy and apply the change reflected in the message to know the current state. As can be seen, MBO/PO messages may carry much more data than MBP/ABV messages because MBO/PO messages reflect information about each order, whereas MBP/ABV messages contain information about orders affecting some predetermined value levels. Furthermore, because specific orders, but not the submitting traders thereof, are identified, other market participants may be able to follow that order as it progresses through the market, e.g., as it is modified, canceled, traded, etc.

An ABV book data object may include information about multiple values. The ABV book data object may be arranged and structured so that information about each value is aggregated together. Thus, for a given value V, the ABV book data object may aggregate all the information by value, such as for example, the number of orders having a certain position at value V, the quantity of total orders resting at value V, etc. Thus, the value field may be the key, or may be a unique field, within an ABV book data object. In one embodiment, the value for each entry within the ABV book data object is different. In one embodiment, information in an ABV book data object is presented in a manner such that the value field is the most granular field of information.

A PO book data object may include information about multiple orders. The PO book data object may be arranged and structured so that information about each order is represented. Thus, for a given order O, the PO book data object may provide all of the information for order O. Thus, the order field may be the key, or may be a unique field, within a PO book data object. In one embodiment, the order ID for each entry within the PO book data object is different. In one embodiment, information in a PO book data object is presented in a manner such that the order field is the most granular field of information.

Thus, the PO book data object may include data about unique orders, e.g., all unique resting orders for a product, and the ABV book data object may include data about unique values, e.g., up to a predetermined level, e.g., top ten price or value levels, for a product.

It should be appreciated that the number, type and manner of market data feeds provided by an electronic trading system are implementation dependent and may vary depending upon the types of products traded by the electronic trading system, customer/trader preferences, bandwidth and data processing limitations, etc. and that all such feeds, now available or later developed, are contemplated herein. MBP/ABV and MBO/PO feeds may refer to categories/variations of market data feeds, distinguished by whether they provide an indication of the current state of a market resulting from a market impacting event (MBP) or an indication of the change in the current state of a market due to a market impacting event (MBO).

Messages, whether MBO or MBP, generated responsive to market impacting events which are caused by a single order, such as a new order, an order cancelation, an order modification, etc., are fairly simple and compact and easily created and transmitted. However, messages, whether MBO or MBP, generated responsive to market impacting events which are caused by more than one order, such as a trade, may require the transmission of a significant amount of data to convey the requisite information to the market participants. For trades involving a large number of orders, e.g., a buy order for a quantity of 5000 which matches 5000 sell orders each for a quantity of 1, a significant amount of information may need to be sent, e.g., data indicative of each of the 5000 trades that have participated in the market impacting event.

In one embodiment, an exchange computing system may generate multiple order book objects, one for each type of view that is published or provided. For example, the system may generate a PO book object and an ABV book object. It should be appreciated that each book object, or view for a product or market, may be derived from the Per Order book object, which includes all the orders for a given financial product or market.

An inbound message may include an order that affects the PO book object, the ABV book object, or both. An outbound message may include data from one or more of the structures within the exchange computing system, e.g., the PO book object queues or the ABV book object queues.

Furthermore, each participating trader needs to receive a notification that their particular order has traded. Continuing with the example, this may require sending 5001 individual trade notification messages, or even 10,000+ messages where each contributing side (buy vs. sell) is separately reported, in addition to the notification sent to all of the market participants.

As detailed in U.S. patent application Ser. No. 14/100,788, the entirety of which is incorporated by reference herein and relied upon, it may be recognized that trade notifications sent to all market participants may include redundant information repeated for each participating trade and a structure of an MBP trade notification message may be provided which results in a more efficient communication of the occurrence of a trade. The message structure may include a header portion which indicates the type of transaction which occurred, i.e., a trade, as well as other general information about the event, an instrument portion which comprises data about each instrument which was traded as part of the transaction, and an order portion which comprises data about each participating order. In one embodiment, the header portion may include a message type, Transaction Time, Match Event Indicator, and Number of Market Data Entries (“No. MD Entries”) fields. The instrument portion may include a market data update action indicator (“MD Update Action”), an indication of the Market Data Entry Type (“MD Entry Type”), an identifier of the instrument/security involved in the transaction (“Security ID”), a report sequence indicator (“Rpt Seq”), the price at which the instrument was traded (“MD Entry PX”), the aggregate quantity traded at the indicated price (“ConsTradeQty”), the number of participating orders (“NumberOfOrders”), and an identifier of the aggressor side (“Aggressor Side”) fields. The order portion may further include an identifier of the participating order (“Order ID”), described in more detail below, and the quantity of the order traded (“MD Entry Size”) fields. It should be appreciated that the particular fields included in each portion are implementation dependent and that different fields in addition to, or in lieu of, those listed may be included depending upon the implementation. It should be appreciated that the exemplary fields can be compliant with the FIX binary and/or FIX/FAST protocol for the communication of the financial information.

The instrument portion contains a set of fields, e.g., seven fields accounting for 23 bytes, which are repeated for each participating instrument. In complex trades, such as trades involving combination orders or strategies, e.g., spreads, or implied trades, there may be multiple instruments being exchanged among the parties. In one embodiment, the order portion includes only one field, accounting for 4 bytes, for each participating order which indicates the quantity of that order which was traded. As will be discussed below, the order portion may further include an identifier of each order, accounting for an additional 8 bytes, in addition to the quantity thereof traded. As should be appreciated, data which would have been repeated for each participating order, is consolidated or otherwise summarized in the header and instrument portions of the message thereby eliminating redundant information and, overall, significantly reducing the size of the message.

While the disclosed embodiments will be discussed with respect to an MBP market data feed, it should be appreciated that the disclosed embodiments may also be applicable to an MBO market data feed.

In one embodiment, the disclosed system may include a Market Segment Gateway (“MSG”) that is the point of ingress/entry and/or egress/departure for all transactions, i.e., the network traffic/packets containing the data therefore, specific to a single market at which the order of receipt of those transactions may be ascribed. An MSG or Market Segment Gateway may be utilized for the purpose of deterministic operation of the market. The electronic trading system may include multiple markets, and because the electronic trading system includes one MSG for each market/product implemented thereby, the electronic trading system may include multiple MSGs. For more detail on deterministic operation in a trading system, see U.S. patent application Ser. No. 14/074,667 entitled “Transactionally Deterministic High Speed Financial Exchange Having Improved, Efficiency, Communication, Customization, Performance, Access, Trading Opportunities, Credit Controls, And Fault Tolerance” and filed on Nov. 7, 2013, the entire disclosure of which is incorporated by reference herein and relied upon.

For example, a participant may send a request for a new transaction, e.g., a request for a new order, to the MSG. The MSG extracts or decodes the request message and determines the characteristics of the request message.

The MSG may include, or otherwise be coupled with, a buffer, cache, memory, database, content addressable memory, data store or other data storage mechanism, or combinations thereof, which stores data indicative of the characteristics of the request message. The request is passed to the transaction processing system, e.g., the match engine.

An MSG or Market Segment Gateway may be utilized for the purpose of deterministic operation of the market. Transactions for a particular market may be ultimately received at the electronic trading system via one or more points of entry, e.g., one or more communications interfaces, at which the disclosed embodiments apply determinism, which as described may be at the point where matching occurs, e.g., at each match engine (where there may be multiple match engines, each for a given product/market, or moved away from the point where matching occurs and closer to the point where the electronic trading system first becomes “aware” of the incoming transaction, such as the point where transaction messages, e.g., orders, ingress the electronic trading system. Generally, the terms “determinism” or “transactional determinism” may refer to the processing, or the appearance thereof, of orders in accordance with defined business rules. Accordingly, as used herein, the point of determinism may be the point at which the electronic trading system ascribes an ordering to incoming transactions/orders relative to other incoming transactions/orders such that the ordering may be factored into the subsequent processing, e.g., matching, of those transactions/orders as will be described. For more detail on deterministic operation in a trading system, see U.S. patent application Ser. No. 14/074,675, filed on Nov. 7, 2013, published as U.S. Patent Publication No. 2015/0127516, entitled “Transactionally Deterministic High Speed Financial Exchange Having Improved, Efficiency, Communication, Customization, Performance, Access, Trading Opportunities, Credit Controls, And Fault Tolerance”, the entirety of which is incorporated by reference herein and relied upon.

Electronic trading of financial instruments, such as futures contracts, is conducted by market participants sending orders, such as to buy or sell one or more futures contracts, in electronic form to the exchange. These electronically submitted orders to buy and sell are then matched, if possible, by the exchange, i.e., by the exchange's matching engine, to execute a trade. Outstanding (unmatched, wholly unsatisfied/unfilled or partially satisfied/filled) orders are maintained in one or more data structures or databases referred to as “order books,” such orders being referred to as “resting,” and made visible, i.e., their availability for trading is advertised, to the market participants through electronic notifications/broadcasts, referred to as market data feeds. An order book is typically maintained for each product, e.g., instrument, traded on the electronic trading system and generally defines or otherwise represents the state of the market for that product, i.e., the current prices at which the market participants are willing buy or sell that product. As such, as used herein, an order book for a product may also be referred to as a market for that product.

Upon receipt of an incoming order to trade in a particular financial instrument, whether for a single-component financial instrument, e.g., a single futures contract, or for a multiple-component financial instrument, e.g., a combination contract such as a spread contract, a match engine, as described herein, will attempt to identify a previously received but unsatisfied order counter thereto, i.e., for the opposite transaction (buy or sell) in the same financial instrument at the same or better price (but not necessarily for the same quantity unless, for example, either order specifies a condition that it must be entirely filled or not at all).

Previously received but unsatisfied orders, i.e., orders which either did not match with a counter order when they were received or their quantity was only partially satisfied, referred to as a partial fill, are maintained by the electronic trading system in an order book database/data structure to await the subsequent arrival of matching orders or the occurrence of other conditions which may cause the order to be modified or otherwise removed from the order book.

If the match engine identifies one or more suitable previously received but unsatisfied counter orders, they, and the incoming order, are matched to execute a trade there between to at least partially satisfy the quantities of one or both the incoming order or the identified orders. If there remains any residual unsatisfied quantity of the identified one or more orders, those orders are left on the order book with their remaining quantity to await a subsequent suitable counter order, i.e., to rest. If the match engine does not identify a suitable previously received but unsatisfied counter order, or the one or more identified suitable previously received but unsatisfied counter orders are for a lesser quantity than the incoming order, the incoming order is placed on the order book, referred to as “resting”, with original or remaining unsatisfied quantity, to await a subsequently received suitable order counter thereto. The match engine then generates match event data reflecting the result of this matching process. Other components of the electronic trading system, as will be described, then generate the respective order acknowledgment and market data messages and transmit those messages to the market participants.

Matching, which is a function typically performed by the exchange, is a process, for a given order which specifies a desire to buy or sell a quantity of a particular instrument at a particular price, of seeking/identifying one or more wholly or partially, with respect to quantity, satisfying counter orders thereto, e.g., a sell counter to an order to buy, or vice versa, for the same instrument at the same, or sometimes better, price (but not necessarily the same quantity), which are then paired for execution to complete a trade between the respective market participants (via the exchange) and at least partially satisfy the desired quantity of one or both of the order and/or the counter order, with any residual unsatisfied quantity left to await another suitable counter order, referred to as “resting.” A match event may occur, for example, when an aggressing order matches with a resting order. In one embodiment, two orders match because one order includes instructions for or specifies buying a quantity of a particular instrument at a particular price, and the other order includes instructions for or specifies selling a (different or same) quantity of the instrument at a same or better price. It should be appreciated that performing an instruction associated with a message may include attempting to perform the instruction. Whether or not an exchange computing system is able to successfully perform an instruction may depend on the state of the electronic marketplace.

While the disclosed embodiments will be described with respect to a product by product or market by market implementation, e.g. implemented for each market/order book, it will be appreciated that the disclosed embodiments may be implemented so as to apply across markets for multiple products traded on one or more electronic trading systems, such as by monitoring an aggregate, correlated or other derivation of the relevant indicative parameters as described herein.

While the disclosed embodiments may be discussed in relation to futures and/or options on futures trading, it should be appreciated that the disclosed embodiments may be applicable to any equity, fixed income security, currency, commodity, options or futures trading system or market now available or later developed. It should be appreciated that a trading environment, such as a futures exchange as described herein, implements one or more economic markets where rights and obligations may be traded. As such, a trading environment may be characterized by a need to maintain market integrity, transparency, predictability, fair/equitable access and participant expectations with respect thereto. In addition, it should be appreciated that electronic trading systems further impose additional expectations and demands by market participants as to transaction processing speed, latency, capacity and response time, while creating additional complexities relating thereto. Accordingly, as will be described, the disclosed embodiments may further include functionality to ensure that the expectations of market participants are met, e.g., that transactional integrity and predictable system responses are maintained.

As was discussed above, electronic trading systems ideally attempt to offer an efficient, fair and balanced market where market prices reflect a true consensus of the value of products traded among the market participants, where the intentional or unintentional influence of any one market participant is minimized if not eliminated, and where unfair or inequitable advantages with respect to information access are minimized if not eliminated.

Financial instrument trading systems allow traders to submit orders and receive confirmations, market data, and other information electronically via electronic messages exchanged using a network. Electronic trading systems ideally attempt to offer a more efficient, fair and balanced market where market prices reflect a true consensus of the value of traded products among the market participants, where the intentional or unintentional influence of any one market participant is minimized if not eliminated, and where unfair or inequitable advantages with respect to information access are minimized if not eliminated.

Electronic marketplaces attempt to achieve these goals by using electronic messages to communicate actions and related data of the electronic marketplace between market participants, clearing firms, clearing houses, and other parties. The messages can be received using an electronic trading system, wherein an action or transaction associated with the messages may be executed. For example, the message may contain information relating to an order to buy or sell a product in a particular electronic marketplace, and the action associated with the message may indicate that the order is to be placed in the electronic marketplace such that other orders which were previously placed may potentially be matched to the order of the received message. Thus the electronic marketplace may conduct market activities through electronic systems.

The clearing house of an exchange clears, settles and guarantees matched transactions in contracts occurring through the facilities of the exchange. In addition, the clearing house establishes and monitors financial requirements for clearing members and conveys certain clearing privileges in conjunction with the relevant exchange markets.

The clearing house establishes clearing level performance bonds (margins) for all products of the exchange and establishes minimum performance bond requirements for customers of such products. A performance bond, also referred to as a margin requirement, corresponds with the funds that must be deposited by a customer with his or her broker, by a broker with a clearing member or by a clearing member with the clearing house, for the purpose of insuring the broker or clearing house against loss on open futures or options contracts. This is not a part payment on a purchase. The performance bond helps to ensure the financial integrity of brokers, clearing members and the exchange as a whole. The performance bond refers to the minimum dollar deposit required by the clearing house from clearing members in accordance with their positions. Maintenance, or maintenance margin, refers to a sum, usually smaller than the initial performance bond, which must remain on deposit in the customer's account for any position at all times. The initial margin is the total amount of margin per contract required by the broker when a futures position is opened. A drop in funds below this level requires a deposit back to the initial margin levels, i.e., a performance bond call. If a customer's equity in any futures position drops to or under the maintenance level because of adverse price action, the broker must issue a performance bond/margin call to restore the customer's equity. A performance bond call, also referred to as a margin call, is a demand for additional funds to bring the customer's account back up to the initial performance bond level whenever adverse price movements cause the account to go below the maintenance.

The exchange derives its financial stability in large part by removing debt obligations among market participants as they occur. This is accomplished by determining a settlement price at the close of the market each day for each contract and marking all open positions to that price, referred to as “mark to market.” Every contract is debited or credited based on that trading session's gains or losses. As prices move for or against a position, funds flow into and out of the trading account. In the case of the CME, each business day by 6:40 a.m. Chicago time, based on the mark-to-the-market of all open positions to the previous trading day's settlement price, the clearing house pays to or collects cash from each clearing member. This cash flow, known as settlement variation, is performed by CME's settlement banks based on instructions issued by the clearing house. All payments to and collections from clearing members are made in “same-day” funds. In addition to the 6:40 a.m. settlement, a daily intra-day mark-to-the market of all open positions, including trades executed during the overnight GLOBEX®, the CME's electronic trading systems, trading session and the current day's trades matched before 11:15 a.m., is performed using current prices. The resulting cash payments are made intra-day for same day value. In times of extreme price volatility, the clearing house has the authority to perform additional intra-day mark-to-the-market calculations on open positions and to call for immediate payment of settlement variation. CME's mark-to-the-market settlement system differs from the settlement systems implemented by many other financial markets, including the interbank, Treasury securities, over-the-counter foreign exchange and debt, options, and equities markets, where participants regularly assume credit exposure to each other. In those markets, the failure of one participant can have a ripple effect on the solvency of the other participants. Conversely, CME's mark-to-the-market system does not allow losses to accumulate over time or allow a market participant the opportunity to defer losses associated with market positions.

While the disclosed embodiments may be described in reference to the CME, it should be appreciated that these embodiments are applicable to any exchange. Such other exchanges may include a clearing house that, like the CME clearing house, clears, settles and guarantees all matched transactions in contracts of the exchange occurring through its facilities. In addition, such clearing houses establish and monitor financial requirements for clearing members and convey certain clearing privileges in conjunction with the relevant exchange markets.

The disclosed embodiments are also not limited to uses by a clearing house or exchange for purposes of enforcing a performance bond or margin requirement. For example, a market participant may use the disclosed embodiments in a simulation or other analysis of a portfolio. In such cases, the settlement price may be useful as an indication of a value at risk and/or cash flow obligation rather than a performance bond. The disclosed embodiments may also be used by market participants or other entities to forecast or predict the effects of a prospective position on the margin requirement of the market participant.

The embodiments may be described in terms of a distributed computing system. The particular examples identify a specific set of components useful in a futures and options exchange. However, many of the components and inventive features are readily adapted to other electronic trading environments. The specific examples described herein may teach specific protocols and/or interfaces, although it should be understood that the principles involved may be extended to, or applied in, other protocols and interfaces.

It should be appreciated that the plurality of entities utilizing or involved with the disclosed embodiments, e.g., the market participants, may be referred to by other nomenclature reflecting the role that the particular entity is performing with respect to the disclosed embodiments and that a given entity may perform more than one role depending upon the implementation and the nature of the particular transaction being undertaken, as well as the entity' s contractual and/or legal relationship with another market participant and/or the exchange.

An exemplary trading network environment for implementing trading systems and methods is shown in FIG. 1. An exchange computer system 100 receives messages that include orders and transmits market data related to orders and trades to users, such as via wide area network 126 and/or local area network 124 and computer devices 114, 116, 118, 120 and 122, as described herein, coupled with the exchange computer system 100.

Herein, the phrase “coupled with” is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software based components. Further, to clarify the use in the pending claims and to hereby provide notice to the public, the phrases “at least one of <A>, <B>, . . . and <N>” or “at least one of <A>, <B>, . . . <N>, or combinations thereof” are defined by the Applicant in the broadest sense, superseding any other implied definitions herebefore or hereinafter unless expressly asserted by the Applicant to the contrary, to mean one or more elements selected from the group comprising A, B, . . . and N, that is to say, any combination of one or more of the elements A, B, . . . or N including any one element alone or in combination with one or more of the other elements which may also include, in combination, additional elements not listed.

The exchange computer system 100 may be implemented with one or more mainframe, desktop or other computers, such as the example computer 200 described herein with respect to FIG. 2. A user database 102 may be provided which includes information identifying traders and other users of exchange computer system 100, such as account numbers or identifiers, user names and passwords. An account data module 104 may be provided which may process account information that may be used during trades.

A match engine module 106 may be included to match bid and offer prices and may be implemented with software that executes one or more algorithms for matching bids and offers. A trade database 108 may be included to store information identifying trades and descriptions of trades. In particular, a trade database may store information identifying the time that a trade took place and the contract price. An order book module 110 may be included to compute or otherwise determine current bid and offer prices, e.g., in a continuous auction market, or also operate as an order accumulation buffer for a batch auction market.

A market data module 112 may be included to collect market data and prepare the data for transmission to users.

A risk management module 134 may be included to compute and determine a user's risk utilization in relation to the user's defined risk thresholds. The risk management module 134 may also be configured to determine risk assessments or exposure levels in connection with positions held by a market participant.

The risk management module 134 may be configured to administer, manage or maintain one or more margining mechanisms implemented by the exchange computer system 100. Such administration, management or maintenance may include managing a number of database records reflective of margin accounts of the market participants. In some embodiments, the risk management module 134 implements one or more aspects of the disclosed embodiments, including, for instance, principal component analysis (PCA) based margining, in connection with interest rate swap (IRS) portfolios, as described herein.

An order processing module 136 may be included to decompose delta-based, spread instrument, bulk and other types of composite orders for processing by the order book module 110 and/or the match engine module 106. The order processing module 136 may also be used to implement one or more procedures related to clearing an order.

A message management module 140 may be included to, among other things, receive, and extract orders from, electronic messages as is indicated with one or more aspects of the disclosed embodiments.

A settlement module 142 (or settlement processor or other payment processor) may be included to provide one or more functions related to settling or otherwise administering transactions cleared by the exchange. Settlement module 142 of the exchange computer system 100 may implement one or more settlement price determination techniques. Settlement-related functions need not be limited to actions or events occurring at the end of a contract term. For instance, in some embodiments, settlement-related functions may include or involve daily or other mark to market settlements for margining purposes. In some cases, the settlement module 142 may be configured to communicate with the trade database 108 (or the memory(ies) on which the trade database 108 is stored) and/or to determine a payment amount based on a spot price, the price of the futures contract or other financial instrument, or other price data, at various times. The determination may be made at one or more points in time during the term of the financial instrument in connection with a margining mechanism. For example, the settlement module 142 may be used to determine a mark to market amount on a daily basis during the term of the financial instrument. Such determinations may also be made on a settlement date for the financial instrument for the purposes of final settlement.

In some embodiments, the settlement module 142 may be integrated to any desired extent with one or more of the other modules or processors of the exchange computer system 100. For example, the settlement module 142 and the risk management module 134 may be integrated to any desired extent. In some cases, one or more margining procedures or other aspects of the margining mechanism(s) may be implemented by the settlement module 142.

It should be appreciated that concurrent processing limits may be defined by or imposed separately or in combination on one or more of the trading system components, including the user database 102, the account data module 104, the match engine module 106, the trade database 108, the order book module 110, the market data module 112, the risk management module 134, the order processing module 136, the message management module 140, the settlement module 142, or other component of the exchange computer system 100.

In an embodiment, the message management module 140, as coupled with the order book module 110, may be configured for receiving a plurality of electronic messages, each of the plurality of messages having an associated action to be executed within a designated period of time having a beginning time and an ending time, wherein at least one electronic message of the plurality of electronic messages comprises data representative of a particular time between the beginning and end of the period of time at which the action associated with the at least one electronic message is to be executed. The exchange computer system 100 may then be further configured to execute the action associated with the at least one temporally specific message at the particular time.

The message management module 140 may define a point of ingress into the exchange computer system 100 where messages are ordered and considered to be received by the system. This may be considered a point of determinism in the exchange computer system 100 that defines the earliest point where the system can ascribe an order of receipt to arriving messages. The point of determinism may or may not be at or near the demarcation point between the exchange computer system 100 and a public/internet network infrastructure. FIG. 3 provides additional details for the message management module 140.

The disclosed mechanisms may be implemented at any logical and/or physical point(s), or combinations thereof, at which the relevant information/data may be monitored or is otherwise accessible or measurable, including one or more gateway devices, modems, the computers or terminals of one or more market participants, etc.

One skilled in the art will appreciate that one or more modules described herein may be implemented using, among other things, a tangible computer-readable medium comprising computer-executable instructions (e.g., executable software code). Alternatively, modules may be implemented as software code, firmware code, specifically configured hardware or processors, and/or a combination of the aforementioned. For example the modules may be embodied as part of an exchange 100 for financial instruments. It should be appreciated the disclosed embodiments may be implemented as a different or separate module of the exchange computer system 100, or a separate computer system coupled with the exchange computer system 100 so as to have access to margin account record, pricing, and/or other data. As described herein, the disclosed embodiments may be implemented as a centrally accessible system or as a distributed system, e.g., where some of the disclosed functions are performed by the computer systems of the market participants.

As shown in FIG. 1, the exchange computer system 100 further includes a message management module 140 which may implement, in conjunction with the market data module 112, the disclosed mechanisms for managing electronic messages containing financial data sent between an exchange and a plurality of market participants, or vice versa. However, as was discussed above, the disclosed mechanisms may be implemented at any logical and/or physical point(s) through which the relevant message traffic, and responses thereto, flows or is otherwise accessible, including one or more gateway devices, modems, the computers or terminals of one or more traders, etc.

FIG. 3 illustrates an embodiment of market order message management as implemented using the message management module 140 and order book module 110 of the exchange computer system 100. As such, a message 10 may be received from a market participant at the exchange computer system 100 by a message receipt module 144 of the message management module 140. The message receipt module 144 processes the message 10 by interpreting the content of the message based on the message transmit protocol, such as the transmission control protocol (“TCP”), to provide the content of the message 10 for further processing by the exchange computer system.

For example, the message management module 140 may determine the transaction type of the transaction requested in a given message. A message may include an instruction to perform a type of transaction. The transaction type may be, in one embodiment, a request/offer/order to either buy or sell a specified quantity or units of a financial instrument at a specified price or value.

Further processing may be performed by the order extraction module 146. The order extraction module 146 may be configured to detect, from the content of the message 10 provided by the message receipt module 144, characteristics of an order for a transaction to be undertaken in an electronic marketplace. For example, the order extraction module 146 may identify and extract order content such as a price, product, volume, and associated market participant for an order. The order extraction module 146 may also identify and extract data indicating an action to be executed by the exchange computer system 100 with respect to the extracted order. The order extraction module may also identify and extract other order information and other actions associated with the extracted order. All extracted order characteristics, other information, and associated actions extracted from a message for an order may be collectively considered an order as described and referenced herein.

Order or message characteristics may include, for example, the state of the system after a message is received, arrival time (e.g., the time a message arrives at the MSG or Market Segment Gateway), message type (e.g., new, modify, cancel), and the number of matches generated by a message. Order or message characteristics may also include market participant side (e.g., buy or sell) or time in force (e.g., a good until end of day order that is good for the full trading day, a good until canceled ordered that rests on the order book until matched, or a fill or kill order that is canceled if not filled immediately).

The order may be communicated from the order extraction module 146 to an order processing module 136. The order processing module 136 may be configured to interpret the communicated order, and manage the order characteristics, other information, and associated actions as they are processed through an order book module 110 and eventually transacted on an electronic market. For example, the order processing module 136 may store the order characteristics and other content and execute the associated actions. In an embodiment, the order processing module may execute an associated action of placing the order into an order book for an electronic trading system managed by the order book module 110. In an embodiment, placing an order into an order book and/or into an electronic trading system may be considered a primary action for an order. The order processing module 136 may be configured in various arrangements, and may be configured as part of the order book module 110, part of the message management module 140, or as an independent functioning module.

The embodiments described herein utilize trade related electronic messages such as mass quote messages, individual order messages, modification messages, cancelation messages, etc., so as to enact trading activity in an electronic market. The trading entity and/or market participant may have one or multiple trading terminals associated with the session. Furthermore, the financial instruments may be financial derivative products. Derivative products may include futures contracts, options on futures contracts, futures contracts that are functions of or related to other futures contracts, swaps, swaptions, or other financial instruments that have their price related to or derived from an underlying product, security, commodity, equity, index, or interest rate product. In one embodiment, the orders are for options contracts that belong to a common option class. Orders may also be for baskets, quadrants, other combinations of financial instruments, etc. The option contracts may have a plurality of strike prices and/or comprise put and call contracts. A mass quote message may be received at an exchange. As used herein, an exchange computing system 100 includes a place or system that receives and/or executes orders.

In an embodiment, a plurality of electronic messages is received from the network. The plurality of electronic messages may be received at a network interface for the electronic trading system. The plurality of electronic messages may be sent from market participants. The plurality of messages may include order characteristics and be associated with actions to be executed with respect to an order that may be extracted from the order characteristics. The action may involve any action as associated with transacting the order in an electronic trading system. The actions may involve placing the orders within a particular market and/or order book of a market in the electronic trading system.

In an embodiment, the market may operate using characteristics that involve collecting orders over a period of time, such as a batch auction market. In such an embodiment, the period of time may be considered an order accumulation period. The period of time may involve a beginning time and an ending time, with orders placed in the market after the beginning time, and the placed order matched at or after the ending time. As such, the action associated with an order extracted from a message may involve placing the order in the market within the period of time. Also, electronic messages may be received prior to or after the beginning time of the period of time.

The electronic messages may also include other data relating to the order. In an embodiment, the other data may be data indicating a particular time in which the action is to be executed. As such, the order may be considered a temporally specific order. The particular time in which an action is undertaken may be established with respect to any measure of absolute or relative time. In an embodiment, the time in which an action is undertaken may be established with reference to the beginning time of the time period or ending time of the time period in a batch auction embodiment. For example, the particular time may be a specific amount of time, such as 10 milliseconds, prior to the ending time of an order accumulation period in the batch auction. Further, the order accumulation period may involve dissecting the accumulation period into multiple consecutive, overlapping, or otherwise divided, sub-periods of time. For example, the sub-periods may involve distinct temporal windows within the order accumulation period. As such, the particular time may be an indicator of a particular temporal window during the accumulation period. For example, the particular time may be specified as the last temporal window prior to the ending time of the accumulation period.

In an embodiment, the electronic message may also include other actions to be taken with respect to the order. These other actions may be actions to be executed after the initial or primary action associated with the order. For example, the actions may involve modifying or canceling an already placed order. Further, in an embodiment, the other data may indicate order modification characteristics. For example, the other data may include a price or volume change in an order. The other actions may involve modifying the already placed order to align with the order modification characteristics, such as changing the price or volume of the already placed order.

In an embodiment, other actions may be dependent actions. For example, the execution of the actions may involve a detection of an occurrence of an event. Such triggering events may be described as other data in the electronic message. For example, the triggering event may be a release of an economic statistic from an organization relating to a product being bought or sold in the electronic market, a receipt of pricing information from a correlated electronic market, a detection of a change in market sentiment derived from identification of keywords in social media or public statements of officials related to a product being bought or sold in the electronic market, and/or any other event or combination of events which may be detected by an electronic trading system.

In an embodiment, the action, or a primary action, associated with an order may be executed. For example, an order extracted from electronic message order characteristics may be placed into a market, or an electronic order book for a market, such that the order may be matched with other orders counter thereto.

In an embodiment involving a market operating using batch auction principles, the action, such as placing the order, may be executed subsequent to the beginning time of the order accumulation period, but prior to the ending time of the order accumulation period. Further, as indicated above, a message may also include other information for the order, such as a particular time the action is to be executed. In such an embodiment, the action may be executed at the particular time. For example, in an embodiment involving a batch auction process having sub-periods during an order accumulation period, an order may be placed during a specified sub-period of the order accumulation period. The disclosed embodiments may be applicable to batch auction processing, as well as continuous processing.

Also, it may be noted that messages may be received prior or subsequent to the beginning time of an order accumulation period. Orders extracted from messages received prior to the beginning time may have the associated actions, or primary actions such as placing the order, executed at any time subsequent to the beginning time, but prior to the ending time, of the order accumulation period when no particular time for the execution is indicated in the electronic message. In an embodiment, messages received prior to the beginning time but not having a particular time specified will have the associated action executed as soon as possible after the beginning time. Because of this, specifying a time for order action execution may allow a distribution and more definite relative time of order placement so as to allow resources of the electronic trading system to operate more efficiently.

In an embodiment, the execution of temporally specific messages may be controlled by the electronic trading system such that a limited or maximum number may be executed in any particular accumulation period, or sub-period. In an embodiment, the order accumulation time period involves a plurality of sub-periods involving distinct temporal windows, a particular time indicated by a message may be indicative of a particular temporal window of the plurality of temporal windows, and the execution of the at least one temporally specific message is limited to the execution of a specified sub-period maximum number of temporally specific messages during a particular sub-period. The electronic trading system may distribute the ability to submit temporally specific message to selected market participants. For example, only five temporally specific messages may be allowed in any one particular period or sub-period. Further, the ability to submit temporally specific messages within particular periods or sub-periods may be distributed based on any technique. For example, the temporally specific messages for a particular sub-period may be auctioned off or otherwise sold by the electronic trading system to market participants. Also, the electronic trading system may distribute the temporally specific messages to preferred market participants, or as an incentive to participate in a particular market.

In an embodiment, an event occurrence may be detected. The event occurrence may be the occurrence of an event that was specified as other information relating to an order extracted from an electronic message. The event may be a triggering event for a modification or cancelation action associated with an order. The event may be detected subsequent to the execution of the first action when an electronic message further comprises the data representative of the event and a secondary action associated with the order. In an embodiment involving a market operating on batch auction principles, the event may be detected subsequent to the execution of a first action, placing an order, but prior to the ending time of an order accumulation period in which the action was executed.

In an embodiment, other actions associated with an order may be executed. The other actions may be any action associated with an order. For example, the action may be a conditional action that is executed in response to a detection of an occurrence of an event. Further, in a market operating using batch auction principles, the conditional action may be executed after the placement of an order during an order accumulation period, but in response to a detection of an occurrence of an event prior to an ending time of the order accumulation period. In such an embodiment, the conditional action may be executed prior to the ending time of the order accumulation period. For example, the placed order may be canceled, or modified using other provided order characteristics in the message, in response to the detection of the occurrence of the event.

An event may be a release of an economic statistic or a fluctuation of prices in a correlated market. An event may also be a perceptible change in market sentiment of a correlated market. A change may be perceptible based on a monitoring of orders or social media for keywords in reference to the market in question. For example, electronic trading systems may be configured to be triggered for action by a use of keywords during a course of ongoing public statements of officials who may be in a position to impact markets, such as Congressional testimony of the Chairperson of the Federal Reserve System.

The other, secondary, or supplemental action may also be considered a modification of a first action executed with respect to an order. For example, a cancelation may be considered a cancelation of the placement of the order. Further, a secondary action may have other data in the message which indicates a specific time in which the secondary action may be executed. The specific time may be a time relative to a first action, or placement of the order, or relative to an accumulation period in a batch auction market. For example, the specific time for execution of the secondary action may be at a time specified relative and prior to the ending period of the order accumulation period. Further, multiple secondary actions may be provided for a single order. Also, with each secondary action a different triggering event may be provided.

In an embodiment, an incoming transaction may be received. The incoming transaction may be from, and therefore associated with, a market participant of an electronic market managed by an electronic trading system. The transaction may involve an order as extracted from a received message, and may have an associated action. The actions may involve placing an order to buy or sell a financial product in the electronic market, or modifying or deleting such an order. In an embodiment, the financial product may be based on an associated financial instrument which the electronic market is established to trade.

In an embodiment, the action associated with the transaction is determined. For example, it may be determined whether the incoming transaction comprises an order to buy or sell a quantity of the associated financial instrument or an order to modify or cancel an existing order in the electronic market. Orders to buy or sell and orders to modify or cancel may be acted upon differently by the electronic market. For example, data indicative of different characteristics of the types of orders may be stored.

In an embodiment, data relating to the received transaction is stored. The data may be stored in any device, or using any technique, operable to store and provide recovery of data. For example, a memory 204 or computer readable medium 210, may be used to store data, as is described with respect to FIG. 2 in further detail herein. Data may be stored relating received transactions for a period of time, indefinitely, or for a rolling most recent time period such that the stored data is indicative of the market participant's recent activity in the electronic market.

If and/or when a transaction is determined to be an order to modify or cancel a previously placed, or existing, order, data indicative of these actions may be stored. For example, data indicative of a running count of a number or frequency of the receipt of modify or cancel orders from the market participant may be stored. A number may be a total number of modify or cancel orders received from the market participant, or a number of modify or cancel orders received from the market participant over a specified time. A frequency may be a time based frequency, as in a number of cancel or modify orders per unit of time, or a number of cancel or modify orders received from the market participant as a percentage of total transactions received from the participant, which may or may not be limited by a specified length of time.

If and/or when a transaction is determined to be an order to buy or sell a financial product, or financial instrument, other indicative data may be stored. For example, data indicative of quantity and associated price of the order to buy or sell may be stored.

Data indicative of attempts to match incoming orders may also be stored. The data may be stored in any device, or using any technique, operable to store and provide recovery of data. For example, a memory 204 or computer readable medium 210, may be used to store data, as is described with respect to FIG. 2. The acts of the process as described herein may also be repeated. As such, data for multiple received transactions for multiple market participants may be stored and used as describe herein.

The order processing module 136 may also store data indicative of characteristics of the extracted orders. For example, the order processing module may store data indicative of orders having an associated modify or cancel action, such as by recording a count of the number of such orders associated with particular market participants. The order processing module may also store data indicative of quantities and associated prices of orders to buy or sell a product placed in the market order book 110, as associated with particular market participants.

Also, the order processing module 136 may be configured to calculate and associate with particular orders a value indicative of an associated market participant's market activity quality, which is a value indicative of whether the market participant's market activity increases or tends to increase liquidity of a market. This value may be determined based on the price of the particular order, previously stored quantities of orders from the associated market participant, the previously stored data indicative of previously received orders to modify or cancel as associated with the market participant, and previously stored data indicative of a result of the attempt to match previously received orders stored in association with the market participant. The order processing module 136 may determine or otherwise calculate scores indicative of the quality value based on these stored extracted order characteristics, such as an MQI as described herein.

Further, electronic trading systems may perform actions on orders placed from received messages based on various characteristics of the messages and/or market participants associated with the messages. These actions may include matching the orders either during a continuous auction process, or at the conclusion of a collection period during a batch auction process. The matching of orders may be by any technique.

The matching of orders may occur based on a priority indicated by the characteristics of orders and market participants associated with the orders. Orders having a higher priority may be matched before orders of a lower priority. This priority may be determined using various techniques. For example, orders that were indicated by messages received earlier may receive a higher priority to match than orders that were indicated by messages received later. Also, scoring or grading of the characteristics may provide for priority determination. Data indicative of order matches may be stored by a match engine and/or an order processing module 136, and used for determining MQI scores of market participants.

Generally, a market may involve market makers, such as market participants who consistently provide bids and/or offers at specific prices in a manner typically conducive to balancing risk, and market takers who may be willing to execute transactions at prevailing bids or offers may be characterized by more aggressive actions so as to maintain risk and/or exposure as a speculative investment strategy. From an alternate perspective, a market maker may be considered a market participant who places an order to sell at a price at which there is no previously or concurrently provided counter order. Similarly, a market taker may be considered a market participant who places an order to buy at a price at which there is a previously or concurrently provided counter order. A balanced and efficient market may involve both market makers and market takers, coexisting in a mutually beneficial basis. The mutual existence, when functioning properly, may facilitate liquidity in the market such that a market may exist with “tight” bid-ask spreads (e.g., small difference between bid and ask prices) and a “deep” volume from many currently provided orders such that large quantity orders may be executed without driving prices significantly higher or lower.

As such, both market participant types are useful in generating liquidity in a market, but specific characteristics of market activity taken by market participants may provide an indication of a particular market participant's effect on market liquidity. For example, a Market Quality Index (“MQI”) of an order may be determined using the characteristics. An MQI may be considered a value indicating a likelihood that a particular order will improve or facilitate liquidity in a market. That is, the value may indicate a likelihood that the order will increase a probability that subsequent requests and transaction from other market participants will be satisfied. As such, an MQI may be determined based on a proximity of the entered price of an order to a midpoint of a current bid-ask price spread, a size of the entered order, a volume or quantity of previously filled orders of the market participant associated with the order, and/or a frequency of modifications to previous orders of the market participant associated with the order. In this way, an electronic trading system may function to assess and/or assign an MQI to received electronic messages to establish messages that have a higher value to the system, and thus the system may use computing resources more efficiently by expending resources to match orders of the higher value messages prior to expending resources of lower value messages.

While an MQI may be applied to any or all market participants, such an index may also be applied only to a subset thereof, such as large market participants, or market participants whose market activity as measured in terms of average daily message traffic over a limited historical time period exceeds a specified number. For example, a market participant generating more than 500, 1,000, or even 10,000 market messages per day may be considered a large market participant.

An exchange provides one or more markets for the purchase and sale of various types of products including financial instruments such as stocks, bonds, futures contracts, options, currency, cash, and other similar instruments. Agricultural products and commodities are also examples of products traded on such exchanges. A futures contract is a product that is a contract for the future delivery of another financial instrument such as a quantity of grains, metals, oils, bonds, currency, or cash. Generally, each exchange establishes a specification for each market provided thereby that defines at least the product traded in the market, minimum quantities that must be traded, and minimum changes in price (e.g., tick size). For some types of products (e.g., futures or options), the specification further defines a quantity of the underlying product represented by one unit (or lot) of the product, and delivery and expiration dates. As will be described, the exchange may further define the matching algorithm, or rules, by which incoming orders will be matched/allocated to resting orders.

Market participants, e.g., traders, use software to send orders or messages to the trading platform. The order identifies the product, the quantity of the product the trader wishes to trade, a price at which the trader wishes to trade the product, and a direction of the order (i.e., whether the order is a bid, i.e., an offer to buy, or an ask, i.e., an offer to sell). It will be appreciated that there may be other order types or messages that traders can send including requests to modify or cancel a previously submitted order.

The exchange computer system monitors incoming orders received thereby and attempts to identify, i.e., match or allocate, as described herein, one or more previously received, but not yet matched, orders, i.e., limit orders to buy or sell a given quantity at a given price, referred to as “resting” orders, stored in an order book database, wherein each identified order is contra to the incoming order and has a favorable price relative to the incoming order. An incoming order may be an “aggressor” order, i.e., a market order to sell a given quantity at whatever may be the current resting bid order price(s) or a market order to buy a given quantity at whatever may be the current resting ask order price(s). An incoming order may be a “market making” order, i.e., a market order to buy or sell at a price for which there are currently no resting orders. In particular, if the incoming order is a bid, i.e., an offer to buy, then the identified order(s) will be an ask, i.e., an offer to sell, at a price that is identical to or higher than the bid price. Similarly, if the incoming order is an ask, i.e., an offer to sell, the identified order(s) will be a bid, i.e., an offer to buy, at a price that is identical to or lower than the offer price.

An exchange computing system may receive conditional orders or messages for a data object, where the order may include two prices or values: a reference value and a stop value. A conditional order may be configured so that when a product represented by the data object trades at the reference price, the stop order is activated at the stop value. For example, if the exchange computing system's order management module includes a stop order with a stop price of 5 and a limit price of 1 for a product, and a trade at 5 (i.e., the stop price of the stop order) occurs, then the exchange computing system attempts to trade at 1 (i.e., the limit price of the stop order). In other words, a stop order is a conditional order to trade (or execute) at the limit price that is triggered (or elected) when a trade at the stop price occurs.

Stop orders also rest on, or are maintained in, an order book to monitor for a trade at the stop price, which triggers an attempted trade at the limit price. In some embodiments, a triggered limit price for a stop order may be treated as an incoming order.

Upon identification (matching) of a contra order(s), a minimum of the quantities associated with the identified order and the incoming order is matched and that quantity of each of the identified and incoming orders become two halves of a matched trade that is sent to a clearing house. The exchange computer system considers each identified order in this manner until either all of the identified orders have been considered or all of the quantity associated with the incoming order has been matched, i.e., the order has been filled. If any quantity of the incoming order remains, an entry may be created in the order book database and information regarding the incoming order is recorded therein, i.e., a resting order is placed on the order book for the remaining quantity to await a subsequent incoming order counter thereto.

It should be appreciated that in electronic trading systems implemented via an exchange computing system, a trade price (or match value) may differ from (i.e., be better for the submitter, e.g., lower than a submitted buy price or higher than a submitted sell price) the limit price that is submitted, e.g., a price included in an incoming message, or a triggered limit price from a stop order.

As used herein, “better” than a reference value means lower than the reference value if the transaction is a purchase transaction, and higher than the reference value if the transaction is a sell transaction. Said another way, for purchase transactions, lower values are better, and for relinquish or sell transactions, higher values are better.

Traders access the markets on a trading platform using trading software that receives and displays at least a portion of the order book for a market, i.e., at least a portion of the currently resting orders, enables a trader to provide parameters for an order for the product traded in the market, and transmits the order to the exchange computer system. The trading software typically includes a graphical user interface to display at least a price and quantity of some of the entries in the order book associated with the market. The number of entries of the order book displayed is generally preconfigured by the trading software, limited by the exchange computer system, or customized by the user. Some graphical user interfaces display order books of multiple markets of one or more trading platforms. The trader may be an individual who trades on his/her behalf, a broker trading on behalf of another person or entity, a group, or an entity. Furthermore, the trader may be a system that automatically generates and submits orders.

If the exchange computer system identifies that an incoming market order may be filled by a combination of multiple resting orders, e.g., the resting order at the best price only partially fills the incoming order, the exchange computer system may allocate the remaining quantity of the incoming, i.e., that which was not filled by the resting order at the best price, among such identified orders in accordance with prioritization and allocation rules/algorithms, referred to as “allocation algorithms” or “matching algorithms,” as, for example, may be defined in the specification of the particular financial product or defined by the exchange for multiple financial products. Similarly, if the exchange computer system identifies multiple orders contra to the incoming limit order and that have an identical price which is favorable to the price of the incoming order, i.e., the price is equal to or better, e.g., lower if the incoming order is a buy (or instruction to purchase) or higher if the incoming order is a sell (or instruction to relinquish), than the price of the incoming order, the exchange computer system may allocate the quantity of the incoming order among such identified orders in accordance with the matching algorithms as, for example, may be defined in the specification of the particular financial product or defined by the exchange for multiple financial products.

An exchange responds to inputs, such as trader orders, cancelation, etc., in a manner as expected by the market participants, such as based on market data, e.g., prices, available counter-orders, etc., to provide an expected level of certainty that transactions will occur in a consistent and predictable manner and without unknown or unascertainable risks. Accordingly, the method by which incoming orders are matched with resting orders must be defined so that market participants have an expectation of what the result will be when they place an order or have resting orders and an incoming order is received, even if the expected result is, in fact, at least partially unpredictable due to some component of the process being random or arbitrary or due to market participants having imperfect or less than all information, e.g., unknown position of an order in an order book. Typically, the exchange defines the matching/allocation algorithm that will be used for a particular financial product, with or without input from the market participants. Once defined for a particular product, the matching/allocation algorithm is typically not altered, except in limited circumstance, such as to correct errors or improve operation, so as not to disrupt trader expectations. It will be appreciated that different products offered by a particular exchange may use different matching algorithms.

For example, a first-in/first-out (FIFO) matching algorithm, also referred to as a “Price Time” algorithm, considers each identified order sequentially in accordance with when the identified order was received. The quantity of the incoming order is matched to the quantity of the identified order at the best price received earliest, then quantities of the next earliest best price orders, and so on until the quantity of the incoming order is exhausted. Some product specifications define the use of a pro-rata matching algorithm, wherein a quantity of an incoming order is allocated to each of plurality of identified orders proportionally. Some exchange computer systems provide a priority to certain standing orders in particular markets. An example of such an order is the first order that improves a price (i.e., improves the market) for the product during a trading session. To be given priority, the trading platform may require that the quantity associated with the order is at least a minimum quantity. Further, some exchange computer systems cap the quantity of an incoming order that is allocated to a standing order on the basis of a priority for certain markets. In addition, some exchange computer systems may give a preference to orders submitted by a trader who is designated as a market maker for the product. Other exchange computer systems may use other criteria to determine whether orders submitted by a particular trader are given a preference. Typically, when the exchange computer system allocates a quantity of an incoming order to a plurality of identified orders at the same price, the trading host allocates a quantity of the incoming order to any orders that have been given priority. The exchange computer system thereafter allocates any remaining quantity of the incoming order to orders submitted by traders designated to have a preference, and then allocates any still remaining quantity of the incoming order using the FIFO or pro-rata algorithms. Pro-rata algorithms used in some markets may require that an allocation provided to a particular order in accordance with the pro-rata algorithm must meet at least a minimum allocation quantity. Any orders that do not meet or exceed the minimum allocation quantity are allocated to on a FIFO basis after the pro-rata allocation (if any quantity of the incoming order remains). More information regarding order allocation may be found in U.S. Pat. No. 7,853,499, the entirety of which is incorporated by reference herein and relied upon.

Other examples of matching algorithms which may be defined for allocation of orders of a particular financial product include:

Price Explicit Time

Order Level Pro Rata

Order Level Priority Pro Rata

Preference Price Explicit Time

Preference Order Level Pro Rata

Preference Order Level Priority Pro Rata

Threshold Pro-Rata

Priority Threshold Pro-Rata

Preference Threshold Pro-Rata

Priority Preference Threshold Pro-Rata

Split Price-Time Pro-Rata

For example, the Price Explicit Time trading policy is based on the basic Price Time trading policy with Explicit Orders having priority over Implied Orders at the same price level. The order of traded volume allocation at a single price level may therefore be:

Explicit order with oldest timestamp first. Followed by

Any remaining explicit orders in timestamp sequence (First In, First Out—FIFO) next. Followed by

Implied order with oldest timestamp next. Followed by

Any remaining implied orders in timestamp sequence (FIFO).

In Order Level Pro Rata, also referred to as Price Pro Rata, priority is given to orders at the best price (highest for a bid, lowest for an offer). If there are several orders at this best price, equal priority is given to every order at this price and incoming business is divided among these orders in proportion to their order size. The Pro Rata sequence of events is:

1. Extract all potential matching orders at best price from the order book into a list.

2. Sort the list by order size, largest order size first. If equal order sizes, oldest timestamp first. This is the matching list.

3. Find the ‘Matching order size, which is the total size of all the orders in the matching list.

4. Find the ‘tradable volume’, which is the smallest of the matching volume and the volume left to trade on the incoming order.

5. Allocate volume to each order in the matching list in turn, starting at the beginning of the list. If all the tradable volume gets used up, orders near the end of the list may not get allocation.

6. The amount of volume to allocate to each order is given by the formula:

(Order volume/Matching volume)*Tradable volume

The result is rounded down (for example, 21.99999999 becomes 21) unless the result is less than 1, when it becomes 1.

7. If tradable volume remains when the last order in the list had been allocated to, return to step 3.

Note: The matching list is not re-sorted, even though the volume has changed. The order which originally had the largest volume is still at the beginning of the list.

8. If there is still volume left to trade on the incoming order, repeat the entire algorithm at the next price level.

Order Level Priority Pro Rata, also referred to as Threshold Pro Rata, is similar to the Price (or ‘Vanilla’) Pro Rata algorithm but has a volume threshold defined. Any pro rata allocation below the threshold will be rounded down to 0. The initial pass of volume allocation is carried out in using pro rata; the second pass of volume allocation is carried out using Price Explicit Time. The Threshold Pro Rata sequence of events is:

1. Extract all potential matching orders at best price from the order book into a list.

2. Sort the list by explicit time priority, oldest timestamp first. This is the matching list.

3. Find the ‘Matching volume’, which is the total volume of all the orders in the matching list.

4. Find the ‘tradable volume’, which is the smallest of the matching volume and the volume left to trade on the incoming order.

5. Allocate volume to each order in the matching list in turn, starting at the beginning of the list.

6. The amount of volume to allocate to each order is given by the formula:

(Order volume/Matching volume)*Tradable volume

The result is rounded down to the nearest lot (for example, 21.99999999 becomes 21) unless the result is less than the defined threshold in which case it is rounded down to 0.

7. If tradable volume remains when the last order in the list had been allocated to, the remaining volume is allocated in time priority to the matching list.

8. If there is still volume left to trade on the incoming order, repeat the entire algorithm at the next price level.

In the Split Price Time Pro-Rata algorithms, a Price Time Percentage parameter is defined. This percentage of the matching volume at each price is allocated by the Price Explicit Time algorithm and the remainder is allocated by the Threshold Pro-Rata algorithm. There are four variants of this algorithm, with and without Priority and/or Preference. The Price Time Percentage parameter is an integer between 1 and 99. (A percentage of zero would be equivalent to using the respective existing Threshold Pro-Rata algorithm, and a percentage of 100 would be equivalent to using the respective existing Price Time algorithm). The Price Time Volume will be the residual incoming volume, after any priority and/or Preference allocation has been made, multiplied by the Price Time Percentage. Fractional parts will be rounded up, so the Price Time Volume will always be at least 1 lot and may be the entire incoming volume. The Price Time Volume is allocated to resting orders in strict time priority. Any remaining incoming volume after the Price Time Volume has been allocated will be allocated according to the respective Threshold Pro-Rata algorithm. The sequence of allocation, at each price level, is therefore:

1. Priority order, if applicable

2. Preference allocation, if applicable

3. Price Time allocation of the configured percentage of incoming volume

4. Threshold Pro-Rata allocation of any remaining incoming volume

5. Final allocation of any leftover lots in time sequence.

Any resting order may receive multiple allocations from the various stages of the algorithm.

It will be appreciated that there may be other allocation algorithms, including combinations of algorithms, now available or later developed, which may be utilized with the disclosed embodiments, and all such algorithms are contemplated herein. In one embodiment, the disclosed embodiments may be used in any combination or sequence with the allocation algorithms described herein.

One exemplary system for matching is described in U.S. patent application Ser. No. 13/534,499, filed on Jun. 27, 2012, entitled “Multiple Trade Matching Algorithms,” published as U.S. Patent Application Publication No. 2014/0006243 A1, the entirety of which is incorporated by reference herein and relied upon, discloses an adaptive match engine which draws upon different matching algorithms, e.g., the rules which dictate how a given order should be allocated among qualifying resting orders, depending upon market conditions, to improve the operation of the market. For example, for a financial product, such as a futures contract, having a future expiration date, the match engine may match incoming orders according to one algorithm when the remaining time to expiration is above a threshold, recognizing that during this portion of the life of the contract, the market for this product is likely to have high volatility. However, as the remaining time to expiration decreases, volatility may decrease. Accordingly, when the remaining time to expiration falls below the threshold, the match engine switches to a different match algorithm which may be designed to encourage trading relative to the declining trading volatility. Thereby, by conditionally switching among matching algorithms within the same financial product, as will be described, the disclosed match engine automatically adapts to the changing market conditions of a financial product, e.g., a limited life product, in a non-preferential manner, maintaining fair order allocation while improving market liquidity, e.g., over the life of the product.

In one implementation, this trading system may evaluate market conditions on a daily basis and, based thereon, change the matching algorithm between daily trading sessions, i.e., when the market is closed, such that when the market reopens, a new trading algorithm is in effect for the particular product. As will be described, the disclosed embodiments may facilitate more frequent changes to the matching algorithms so as to dynamically adapt to changing market conditions, e.g., intra-day changes, and even intra-order matching changes. It will be further appreciated that hybrid matching algorithms, which match part of an order using one algorithm and another part of the order using a different algorithm, may also be used.

With respect to incoming orders, some traders, such as automated and/or algorithmic traders, attempt to respond to market events, such as to capitalize upon a mispriced resting order or other market inefficiency, as quickly as possible. This may result in penalizing the trader who makes an errant trade, or whose underlying trading motivations have changed, and who cannot otherwise modify or cancel their order faster than other traders can submit trades there against. It may considered that an electronic trading system that rewards the trader who submits their order first creates an incentive to either invest substantial capital in faster trading systems, participate in the market substantially to capitalize on opportunities (aggressor side/lower risk trading) as opposed to creating new opportunities (market making/higher risk trading), modify existing systems to streamline business logic at the cost of trade quality, or reduce one's activities and exposure in the market. The result may be a lesser quality market and/or reduced transaction volume, and corresponding thereto, reduced fees to the exchange.

With respect to resting orders, allocation/matching suitable resting orders to match against an incoming order can be performed, as described herein, in many different ways. Generally, it will be appreciated that allocation/matching algorithms are only needed when the incoming order quantity is less than the total quantity of the suitable resting orders as, only in this situation, is it necessary to decide which resting order(s) will not be fully satisfied, which trader(s) will not get their orders filled. It can be seen from the above descriptions of the matching/allocation algorithms, that they fall generally into three categories: time priority/first-in-first-out (“FIFO”), pro rata, or a hybrid of FIFO and pro rata.

As described above, matching systems apply a single algorithm, or combined algorithm, to all of the orders received for a particular financial product to dictate how the entire quantity of the incoming order is to be matched/allocated. In contrast, the disclosed embodiments may apply different matching algorithms, singular or combined, to different orders, as will be described, recognizing that the allocation algorithms used by the trading host for a particular market may, for example, affect the liquidity of the market. Specifically, some allocation algorithms may encourage traders to submit more orders, where each order is relatively small, while other allocation algorithms encourage traders to submit larger orders. Other allocation algorithms may encourage a trader to use an electronic trading system that can monitor market activity and submit orders on behalf of the trader very quickly and without intervention. As markets and technologies available to traders evolve, the allocation algorithms used by trading hosts must also evolve accordingly to enhance liquidity and price discovery in markets, while maintaining a fair and equitable market.

FIFO generally rewards the first trader to place an order at a particular price and maintains this reward indefinitely. So if a trader is the first to place an order at price X, no matter how long that order rests and no matter how many orders may follow at the same price, as soon as a suitable incoming order is received, that first trader will be matched first. This “first mover” system may commit other traders to positions in the queue after the first move traders. Furthermore, while it may be beneficial to give priority to a trader who is first to place an order at a given price because that trader is, in effect, taking a risk, the longer that the trader's order rests, the less beneficial it may be. For instance, it could deter other traders from adding liquidity to the marketplace at that price because they know the first mover (and potentially others) already occupies the front of the queue.

With a pro rata allocation, incoming orders are effectively split among suitable resting orders. This provides a sense of fairness in that everyone may get some of their order filled. However, a trader who took a risk by being first to place an order (a “market turning” order) at a price may end up having to share an incoming order with a much later submitted order. Furthermore, as a pro rata allocation distributes the incoming order according to a proportion based on the resting order quantities, traders may place orders for large quantities, which they are willing to trade but may not necessarily want to trade, in order to increase the proportion of an incoming order that they will receive. This results in an escalation of quantities on the order book and exposes a trader to a risk that someone may trade against one of these orders and subject the trader to a larger trade than they intended. In the typical case, once an incoming order is allocated against these large resting orders, the traders subsequently cancel the remaining resting quantity which may frustrate other traders. Accordingly, as FIFO and pro rata both have benefits and problems, exchanges may try to use hybrid allocation/matching algorithms which attempt to balance these benefits and problems by combining FIFO and pro rata in some manner. However, hybrid systems define conditions or fixed rules to determine when FIFO should be used and when pro rata should be used. For example, a fixed percentage of an incoming order may be allocated using a FIFO mechanism with the remainder being allocated pro rata.

Traders trading on an exchange including, for example, exchange computer system 100, often desire to trade multiple financial instruments in combination. Each component of the combination may be called a leg. Traders can submit orders for individual legs or in some cases can submit a single order for multiple financial instruments in an exchange-defined combination. Such orders may be called a strategy order, a spread order, or a variety of other names.

A spread instrument may involve the simultaneous purchase of one security and sale of a related security, called legs, as a unit. The legs of a spread instrument may be options or futures contracts, or combinations of the two. Trades in spread instruments are executed to yield an overall net position whose value, called the spread, depends on the difference between the prices of the legs. Spread instruments may be traded in an attempt to profit from the widening or narrowing of the spread, rather than from movement in the prices of the legs directly. Spread instruments are either “bought” or “sold” depending on whether the trade will profit from the widening or narrowing of the spread, respectively. An exchange often supports trading of common spreads as a unit rather than as individual legs, thus ensuring simultaneous execution of the two legs, eliminating the execution risk of one leg executing but the other failing.

One example of a spread instrument is a calendar spread instrument. The legs of a calendar spread instrument differ in delivery date of the underlier. The leg with the earlier occurring delivery date is often referred to as the lead month contract. A leg with a later occurring delivery date is often referred to as a deferred month contract. Another example of a spread instrument is a butterfly spread instrument, which includes three legs having different delivery dates. The delivery dates of the legs may be equidistant to each other. The counterparty orders that are matched against such a combination order may be individual, “outright” orders or may be part of other combination orders.

In other words, an exchange may receive, and hold or let rest on the books, outright orders for individual contracts as well as outright orders for spreads associated with the individual contracts. An outright order (for either a contract or for a spread) may include an outright bid or an outright offer, although some outright orders may bundle many bids or offers into one message (often called a mass quote).

A spread is an order for the price difference between two contracts. This results in the trader holding a long and a short position in two or more related futures or options on futures contracts, with the objective of profiting from a change in the price relationship. A typical spread product includes multiple legs, each of which may include one or more underlying financial instruments. A butterfly spread product, for example, may include three legs. The first leg may consist of buying a first contract. The second leg may consist of selling two of a second contract. The third leg may consist of buying a third contract. The price of a butterfly spread product may be calculated as:

Butterfly=Leg1−2×Leg2+Leg3   (equation 1)

In the above equation, Leg1 equals the price of the first contract, Leg2 equals the price of the second contract and Leg3 equals the price of the third contract. Thus, a butterfly spread could be assembled from two inter-delivery spreads in opposite directions with the center delivery month common to both spreads.

A calendar spread, also called an intra-commodity spread, for futures is an order for the simultaneous purchase and sale of the same futures contract in different contract months (i.e., buying a September CME S&P 500® futures contract and selling a December CME S&P 500 futures contract).

A crush spread is an order, usually in the soybean futures market, for the simultaneous purchase of soybean futures and the sale of soybean meal and soybean oil futures to establish a processing margin. A crack spread is an order for a specific spread trade involving simultaneously buying and selling contracts in crude oil and one or more derivative products, typically gasoline and heating oil. Oil refineries may trade a crack spread to hedge the price risk of their operations, while speculators attempt to profit from a change in the oil/gasoline price differential.

A straddle is an order for the purchase or sale of an equal number of puts and calls, with the same strike price and expiration dates. A long straddle is a straddle in which a long position is taken in both a put and a call option. A short straddle is a straddle in which a short position is taken in both a put and a call option. A strangle is an order for the purchase of a put and a call, in which the options have the same expiration and the put strike is lower than the call strike, called a long strangle. A strangle may also be the sale of a put and a call, in which the options have the same expiration and the put strike is lower than the call strike, called a short strangle. A pack is an order for the simultaneous purchase or sale of an equally weighted, consecutive series of four futures contracts, quoted on an average net change basis from the previous day's settlement price. Packs provide a readily available, widely accepted method for executing multiple futures contracts with a single transaction. A bundle is an order for the simultaneous sale or purchase of one each of a series of consecutive futures contracts. Bundles provide a readily available, widely accepted method for executing multiple futures contracts with a single transaction.

Thus an exchange may match outright orders, such as individual contracts or spread orders (which as discussed herein could include multiple individual contracts). The exchange may also imply orders from outright orders. For example, exchange computer system 100 may derive, identify and/or advertise, publish, display or otherwise make available for trading orders based on outright orders.

For example, two different outright orders may be resting on the books, or be available to trade or match. The orders may be resting because there are no outright orders that match the resting orders. Thus, each of the orders may wait or rest on the books until an appropriate outright counteroffer comes into the exchange or is placed by a user of the exchange. The orders may be for two different contracts that only differ in delivery dates. It should be appreciated that such orders could be represented as a calendar spread order. Instead of waiting for two appropriate outright orders to be placed that would match the two existing or resting orders, the exchange computer system may identify a hypothetical spread order that, if entered into the system as a tradable spread order, would allow the exchange computer system to match the two outright orders. The exchange may thus advertise or make available a spread order to users of the exchange system that, if matched with a tradable spread order, would allow the exchange to also match the two resting orders. Thus, the match engine is configured to detect that the two resting orders may be combined into an order in the spread instrument and accordingly creates an implied order.

In other words, the exchange's matching system may imply the counteroffer order by using multiple orders to create the counteroffer order. Examples of spreads include implied IN, implied OUT, 2nd- or multiple-generation, crack spreads, straddle, strangle, butterfly, and pack spreads. Implied IN spread orders are derived from existing outright orders in individual legs. Implied OUT outright orders are derived from a combination of an existing spread order and an existing outright order in one of the individual underlying legs. Implied orders can fill in gaps in the market and allow spreads and outright futures traders to trade in a product where there would otherwise have been little or no available bids and asks.

For example, implied IN spreads may be created from existing outright orders in individual contracts where an outright order in a spread can be matched with other outright orders in the spread or with a combination of orders in the legs of the spread. An implied OUT spread may be created from the combination of an existing outright order in a spread and an existing outright order in one of the individual underlying leg. An implied IN or implied OUT spread may be created when an electronic match system simultaneously works synthetic spread orders in spread markets and synthetic orders in the individual leg markets without the risk to the trader/broker of being double filled or filled on one leg and not on the other leg.

By linking the spread and outright markets, implied spread trading increases market liquidity. For example, a buy in one contract month and an offer in another contract month in the same futures contract can create an implied market in the corresponding calendar spread. An exchange may match an order for a spread product with another order for the spread product. Some existing exchanges attempt to match orders for spread products with multiple orders for legs of the spread products. With such systems, every spread product contract is broken down into a collection of legs and an attempt is made to match orders for the legs. Examples of implied spread trading include those disclosed in U.S. Patent Publication No. 2005/0203826, entitled “Implied Spread Trading System,” the entire disclosure of which is incorporated by reference herein and relied upon. Examples of implied markets include those disclosed in U.S. Pat. No. 7,039,610, entitled “Implied Market Trading System,” the entire disclosure of which is incorporated by reference herein and relied upon.

As an intermediary to electronic trading transactions, the exchange bears a certain amount of risk in each transaction that takes place. To that end, the clearing house implements risk management mechanisms to protect the exchange. One or more of the modules of the exchange computer system 100 may be configured to determine settlement prices for constituent contracts, such as deferred month contracts, of spread instruments, such as for example, settlement module 142.

One or more of the above-described modules of the exchange computer system 100 may be used to gather or obtain data to support the settlement price determination, as well as a subsequent margin requirement determination. For example, the order book module 110 and/or the market data module 112 may be used to receive, access, or otherwise obtain market data, such as bid-offer values of orders currently on the order books. The trade database 108 may be used to receive, access, or otherwise obtain trade data indicative of the prices and volumes of trades that were recently executed in a number of markets. In some cases, transaction data (and/or bid/ask data) may be gathered or obtained from open outcry pits and/or other sources and incorporated into the trade and market data from the electronic trading system(s).

In some cases, the outright market for the deferred month or other constituent contract may not be sufficiently active to provide market data (e.g., bid-offer data) and/or trade data. Spread instruments involving such contracts may nonetheless be made available by the exchange. The market data from the spread instruments may then be used to determine a settlement price for the constituent contract. The settlement price may be determined, for example, through a boundary constraint-based technique based on the market data (e.g., bid-offer data) for the spread instrument, as described in U.S. Patent Publication No. 2015/0073962 entitled “Boundary Constraint-Based Settlement in Spread Markets” (“the '962 Publication”), the entire disclosure of which is incorporated by reference herein and relied upon. Settlement price determination techniques may be implemented to cover calendar month spread instruments having different deferred month contracts.

In one embodiment, the messages and/or values received for each object may be stored in queues according to value and/or priority techniques implemented by an exchange computing system 100. FIG. 4A illustrates an example data structure 400, which may be stored in a memory or other storage device, such as the memory 204 or storage device 206 described above with respect to FIG. 2, for storing and retrieving messages related to different values for the same action for an object. For example, data structure 400 may be a set of queues or linked lists for multiple values for an action, e.g., bid, on an object. Data structure 400 may be implemented as a database. It should be appreciated that the system may store multiple values for the same action for an object, for example, because multiple users submitted messages to buy specified quantities of an object at different values. Thus, in one embodiment, the exchange computing system can keep track of different orders or messages for buying or selling quantities of objects at specified values.

Although the application contemplates using queue data structures for storing messages in a memory, the implementation may involve additional pointers, i.e., memory address pointers, or linking to other data structures. Thus, in one embodiment, each queue may store different values, which could represent prices, where each value points to or is linked to the messages (which may themselves be stored in queues and sequenced according to priority techniques, such as prioritizing by value) that will match at that value. For example, as shown in FIG. 4A, all of the values relevant to executing an action at different values for an object are stored in a queue. Each value in turn points to, e.g., a linked list or queue logically associated with the values. The linked list stores the messages that instruct the exchange computing system to buy specified quantities of the object at the corresponding value.

The sequence of the messages in the message queues connected to each value may be determined by exchange implemented priority techniques. For example, in FIG. 4A, messages M1, M2, M3 and M4 are associated with performing an action (e.g., buying or selling) a certain number of units (may be different for each message) at Value 1. M1 has priority over M2, which has priority over M3, which has priority over M4. Thus, if a counter order matches at Value 1, the system fills as much quantity as possible associated with M1 first, then M2, then M3, and then M4.

In the illustrated examples, the values may be stored in sequential order, and the best or lead value for a given queue may be readily retrievable by and/or accessible to the disclosed routing system. Thus, in one embodiment, the value having the best priority may be illustrated as being in the topmost position in a queue, although the system may be configured to place the best priority message in some other predetermined position. In the example of FIG. 4A, Value 1 is shown as being the best value or lead value, or the top of the book value, for an example Action. In one embodiment, as discussed herein, the disclosed routing system may access the top of book information for a given action in a queue to determine whether a message betters or improves the queue for an object.

FIG. 4B illustrates an example alternative data structure 450 for storing and retrieving messages and related values. It should be appreciated that matches occur based on values, and so all the messages related to a given value may be prioritized over all other messages related to a different value. As shown in FIG. 4B, the messages may be stored in one queue and grouped by values according to the hierarchy of the values. The hierarchy of the values may depend on the action to be performed.

For example, if a queue is a sell queue (e.g., the Action is Sell), the lowest value may be given the best priority and the highest value may be given the lowest priority. Thus, as shown in FIG. 4B, if Value 1 is lower than Value 2 which is lower than Value 3, Value 1 messages may be prioritized over Value 2, which in turn may be prioritized over Value 3.

Within Value 1, Ml is prioritized over M2, which in turn is prioritized over M3, which in turn is prioritized over M4. Within Value 2, M5 is prioritized over M6, which in turn is prioritized over M7, which in turn is prioritized over M8. Within Value 3, M9 is prioritized over M10, which in turn is prioritized over M11, which in turn is prioritized over M12.

Alternatively, the messages may be stored in a tree-node data structure that defines the priorities of the messages. In one embodiment, the messages may make up the nodes.

In one embodiment, the system may traverse through a number of different values and associated messages when processing an incoming message. Traversing values may involve the processor loading each value, checking that value and deciding whether to load another value, i.e., by accessing the address pointed at by the address pointer value. In particular, referring to FIG. 4B, if the queue is for selling an object for the listed Values 1, 2 and 3 (where Value 1 is lower than Value 2 which is lower than Value 3), and if the system receives an incoming aggressing order to buy quantity X at a Value 4 that is greater than Values 1, 2, and 3, the system will fill as much of quantity X as possible by first traversing through the messages under Value 1 (in sequence M1, M2, M3, M4). If any of the quantity of X remains, the system traverses down the prioritized queue until all of the incoming order is filled (e.g., all of X is matched) or until all of the quantities of M1 through M12 are filled. Any remaining, unmatched quantity remains on the books, e.g., as a resting order at Value 4, which was the entered value or the message's value.

The system may traverse the queues and check the values in a queue, and upon finding the appropriate value, may locate the messages involved in making that value available to the system. When an outright message value is stored in a queue, and when that outright message is involved in a trade or match, the system may check the queue for the value, and then may check the data structure storing messages associated with that value.

In one embodiment, an exchange computing system may convert all financial instruments to objects. In one embodiment, an object may represent the order book for a financial instrument. Moreover, in one embodiment, an object may be defined by two queues, one queue for each action that can be performed by a user on the object. For example, an order book converted to an object may be represented by an Ask queue and a Bid queue. Resting messages or orders associated with the respective financial instrument may be stored in the appropriate queue and recalled therefrom.

In one embodiment, the messages associated with objects may be stored in specific ways depending on the characteristics of the various messages and the states of the various objects in memory. For example, a system may hold certain resting messages in queue until the message is to be processed, e.g., the message is involved in a match. The order, sequence or priority given to messages may depend on the characteristics of the message. For example, in certain environments, messages may indicate an action that a computer in the system should perform. Actions may be complementary actions, or require more than one message to complete. For example, a system may be tasked with matching messages or actions contained within messages. The messages that are not matched may be queued by the system in a data queue or other structure, e.g., a data tree having nodes representing messages or orders. Again, the best value for a given queue may be readily retrievable by and/or accessible to the disclosed routing system.

The queues are structured so that the messages are stored in sequence according to priority. Although the embodiments are disclosed as being implemented in queues, it should be understood that different data structures such as for example linked lists or trees may also be used.

The system may include separate data structures, e.g., queues, for different actions associated with different objects within the system. For example, in one embodiment, the system may include a queue for each possible action that can be performed on an object. The action may be associated with a value. The system prioritizes the actions based in part on the associated value.

For example, as shown in FIG. 4C, the order book module of a computing system may include several paired queues, such as queues Bid and Ask for an object 402 (e.g., Object A). The system may include two queues, or one pair of queues, for each object that is matched or processed by the system. In one embodiment, the system stores messages in the queues that have not yet been matched or processed. FIG. 4C may be an implementation of the data structures disclosed in FIGS. 4A and/or 4B. Each queue may have a top of book, or lead, position, such as positions 404 and 406, which stores data that is retrieved by the disclosed routing system.

The queues may define the priority or sequence in which messages are processed upon a match event. For example, two messages stored in a queue may represent performing the same action at the same value. When a third message is received by the system that represents a matching action at the same value, the system may need to select one of the two waiting, or resting, messages as the message to use for a match. Thus, when multiple messages can be matched at the same value, the exchange may have a choice or some flexibility regarding the message that is matched. The queues may define the priority in which orders that are otherwise equivalent (e.g., same action for the same object at the same value) are processed.

The system may include a pair of queues for each object, e.g., a bid and ask queue for each object. Each queue may be for example implemented utilizing the data structure of FIG. 4B. The exchange may be able to specify the conditions upon which a message for an object should be placed in a queue. For example, the system may include one queue for each possible action that can be performed on an object. The system may be configured to process messages that match with each other. In one embodiment, a message that indicates performing an action at a value may match with a message indicating performing a corresponding action at the same value. Or, the system may determine the existence of a match when messages for the same value exist in both queues of the same object.

The messages may be received from the same or different users or traders.

The queues illustrated in FIG. 4C hold or store messages received by a computing exchange, e.g., messages submitted by a user to the computing exchange, and waiting for a proper match. It should be appreciated that the queues may also hold or store implieds, e.g., implied messages generated by the exchange system, such as messages implied in or implied out as described herein. The system thus adds messages to the queues as they are received, e.g., messages submitted by users, or generated, e.g., implied messages generated by the exchanges. The sequence or prioritization of messages in the queues is based on information about the messages and the overall state of the various objects in the system.

The disclosed embodiments relate to data dissemination via electronic messages and data feeds, such as messages generated by an exchange computing system and sent to market participants, e.g., market data feeds.

FIG. 5 illustrates an example exchange computing system 500 including multiple objects representing books or views of products, including Per Order Book Object 502 and Aggregated by Value Book Object 504. Exchange computing system 500 may receive an inbound message 506, which includes instructions or information about an order for a product associated with the PO Book Object 502 and the ABV Book Object 504. For example, the inbound message 506 may include instructions to perform a transaction on a financial product, which is may be represented by the book objects 502 and 504.

The book objects may be in communication with each other. In one embodiment, Book Objects 502 and 504 may depend on each other, i.e., Book Object 504 may be derived from Book Object 502. The instructions may cause the addition, modification, or cancellation of an order associated with the PO Book Object 502, which may in turn impact a value level represented by the ABV Book Object 504.

Alternatively, in one embodiment, Book Objects 502 and 504 may be independent of each other, i.e., Book Object 504 may not be derived from Book Object 502. The instructions received via inbound message 506 may directly impact the two book objects 502 and 504.

In one example, the instructions may cause one or more events to occur, e.g., a match event, or a modification to a book object event. For example, if the instructions do not cause a match event, the instructions may cause an add event, e.g., they may generate an order to be added to the order book, i.e., an order associated with the inbound message may become a resting order that is added to the PO Book Object 502. If the value associated with the order associated with the inbound message is a value that exists in the ABV Book Object 504, the order associated with the inbound message may cause modification of the information in the ABV Book Object as well.

The exchange computing system may determine whether one or more book data objects have been modified, and may generate data indicating the modifications. The exchange computing system may additionally generate messages including the data indicating the modifications to the data objects.

In one embodiment, the exchange computing system 500 may store multiple versions or instances of a book object, representing the book object at different times, e.g., before and after performing a transaction based on inbound message 506. For example, the exchange computing system 500 may store initial and resulting order book objects 502 and 508 respectively. The exchange computing system may store initial PO book object 502 in memory. Upon receipt of an inbound message 506, which may cause the occurrence of an event that updates or changes book objects, the exchange computing system may modify book object 502, resulting in PO book object 508. Similarly, the exchange computing system may store initial ABV book object 504 in memory. Upon receipt of an inbound message 506, the exchange computing system may modify book object 504, resulting in a resulting ABV book object 510.

As discussed with reference to FIGS. 4A, 4B and 4C, an order book, in one embodiment, may be implemented as a collection of queues, e.g., queues of Ask resting orders and Buy resting orders, for a financial product.

In one embodiment, the exchange computing system 500 may be configured so that any change to a book causes the generation of a message reporting the change. For example, changes to an order in the PO Book Object 502, or changes to a quantity associated with a value level represented by the ABV Book Object 504, may cause the generation of a PO Book message and/or an ABV Book message, respectively, that is published to data recipient computing systems via PO data feed 512 and/or ABV data feed 514, respectively.

Accordingly, in one embodiment, an exchange computing system 500 may include an order book module that maintains/stores, in a memory in communication with the order book module, different types of views or perspectives of the positions for a product, such as a Per Order book or a By Value book. The exchange computing system 500 may also include a data generation module that generates outbound messages if inbound messages cause the modification of any of the book objects stored in association with the order book module. For example, a data generation module may generate a Per Order format message whenever the Per Order Book Object is modified and/or may generate an Aggregated by Value format message whenever the Aggregated by Value Book Object is modified.

In one embodiment, a data recipient computing system that consumes, or reads, PO or ABV messages may apply the data in the received messages to a locally maintained copy of a PO or ABV book object, respectively. It should be understood that a copy locally maintained by a data recipient computing system is independent of the order book object maintained and utilized by the exchange computing system. Thus, a recipient computing system may maintain its own copy of book objects, and apply changes indicated by received messages, e.g., via data feeds, to the object in order to arrive at the most current or accurate state of the book object.

It should be appreciated that the types of outbound financial messages transmitted to data recipient computing systems dictate how the messages are consumed and interpreted by the recipient system. In one embodiment, different message types, e.g., PO messages and ABV messages, require different receiving systems, or recipient computing systems that are configured differently. It should be appreciated that it may be necessary for a recipient computing system to be specifically configured to receive and decipher specific message types, e.g., a data recipient computing system may need different configurations to receive different types of messages.

FIGS. 6A and 6B illustrate example message structures of different message types that may be generated by a data generation module and disseminated via data feeds by the exchange computing system to data recipient computing systems.

FIG. 6A illustrates an example ABV message 600, which includes information aggregated by value about a data object representing positions for a financial product. An example ABV message may include a header portion 602, which indicates a message sequence, sending time, message type, a transaction time, an event indicator, and the number of entries. The header portion 602 may be considered to provide or include general information about the message.

The ABV message 600 also includes a body portion 604 which indicates a value at which several orders have been aggregated in the ABV message, the quantity aggregated at the value, the subject security or product, a sequence number, the number of orders aggregated in the ABV message, the value level (e.g., first, second, etc.), the action to be performed on the associated ABV book data object, and a side (e.g., Buy or Sell). In particular, the example ABV message 600 body portion 604 indicates that the ABV book object includes an entry for Buying Security or Product CLH6 at a Price or Value 29.5 (which is the topmost or level 1 Value Level), which is associated with a Quantity of 10, and the Number of Orders is 1. If the exchange computing system subsequently receives an order to buy a quantity of 18 for the same security at the same price or value level, this order may then be added to the ABV book. The exchange computing system may generate a new ABV message (not shown) indicating that the ABV book object entry for Buying Security or Product CLH6 at a Price or Value 29.5 is now associated with a Quantity of 28 (10 plus 18), and the Number of Order is 2 (1 plus 1).

Column 606 indicates the size of each of the ABV message fields. Column 608 indicates the total sizes of the header portion 602 and body portion 604. As shown in FIG. 6A, the example ABV message is 56 bytes, namely, 24 bytes (header portion 602) plus 32 bytes (body portion 604).

In one embodiment, as may be understood in the art, message sizes are multiples of 8 bytes due to typical computer (both exchange computing system and data recipient computing system) architectural specifications. Thus, even though example ABV message body portion 604 includes 27 bytes of information, the body portion sizing is increased to the next multiple of 8, namely, 32 bytes.

FIG. 6B illustrates an example PO message 610, which conveys information about orders in a data object representing positions for a financial product. An example PO message may include a header portion 612, which, like ABV message header portion 602, indicates a message sequence, sending time, message type, a transaction time, an event indicator, and the number of entries, and may be considered to provide or include general information about the message.

The PO message 610 also includes a body portion 614 which indicates a value associated with a subject order represented in the PO message, the order quantity, the subject security or product, a sequence number, an order ID for the subject order, a priority for the subject order, the action to be performed on the associated PO book data object, and a side (e.g., Buy or Sell). In particular, the example PO message 610 body portion 614 indicates that the subject order is Order ID 123, an order to Buy a Quantity of 10 of Security or Product CLH6 at Price or Value 29.45, having Priority 1234. If the exchange computing system subsequently receives a message from a trader computer to modify Order ID 123 to have a Quantity of 15, this new message would cause modification of the PO book data object. The exchange computing system may generate a new PO message (not shown) indicated that the PO book object entry for Order ID 123 is now associated with a Quantity of 15.

Column 616 indicates the size of each of the PO message fields. Column 618 indicates the total sizes of the header portion 612 and body portion 614. As shown in FIG. 6B, the example PO message is 64 bytes, namely, 24 bytes (header portion 612) plus 40 bytes (body portion 614). Even though example PO message body portion 614 includes 38 bytes of information, the body portion sizing is increased to the next multiple of 8, namely, 40 bytes, due to computing architectural specifications discussed herein.

It should be appreciated that messages, whether of a first type (e.g., ABV) or a second type (e.g., PO), may be generated responsive to book impacting events. The messages may be caused by an event that is associated with a single incoming order, such as a new order, an order cancelation, an order modification, etc. Alternatively, the messages may be caused by an event associated with multiple orders, such as a trade or match between multiple orders.

The same event may cause the generation of both ABV message 600 and PO message 610. In some cases, an event may cause only the generation of PO message 610. As discussed herein, match engine module 106 receives messages and performs actions according to the instructions contained therein. In one embodiment, the actions performed by match engine module 106 determine the events that cause the generation of data feed messages.

For example, if the match engine module determines that a received message matches with orders resting on the books, the exchange computing system may generate both PO messages and ABV messages describing the match event.

Or, if the match engine module determines that a received message does not match with any of the orders resting on the books, a new order may simply be added to the books. The addition of the new order would cause the generation of a PO message. If the newly added order is at a value level that impacts the ABV book data object, the exchange computing system (e.g., order book module 110 and/or data generation module 112) may additionally generate an ABV message.

In one embodiment, the exchange computing system may determine limit values (whether they be incoming limit orders, modifications of previous limit orders, or triggered limit values from a conditional order) and/or trade values (the value at which a quantity is actually matched or executed) associated with a message, depending on whether the message is fully matched, partially matched, or not matched at all.

In one embodiment, a match engine module may attempt to match a submitted value (e.g., a price included in an inbound electronic data transaction request message, or a triggered limit price from a stop order in a previously received electronic data transaction request message). In other words, values submitted to a match engine module may be values received via inbound messages (e.g., a limit price on a new incoming order, or a modification of a previous order), or recently triggered messages (e.g., a limit price in a stop order resting on the books that is triggered by a trade at the stop price).

In one embodiment, a stop order is not added to a PO book data object until the stop ordered is triggered, e.g., triggered by a trade at the stop price. If a stop ordered is triggered, e.g., changed to a limit order upon being triggered by a trade at the stop price, the new limit order is added to the PO book data object. The new limit order may additionally be added to the ABV book data object depending on the value associated with the limit order, e.g., depending on whether the value associated with the limit order is a value level that exists in the ABV book data object, or should be added to the ABV book data object.

The system may determine a trade value for each message, which may be the same or different than a submitted value. For example, a new incoming message may include an instruction to purchase 5 units of a product at a value of 7. Or, a conditional message may be triggered which includes an instruction to purchase 5 units of a product at a value of 7. In both cases (whether a new incoming message or a triggered conditional message), the submitted value may be considered to be 7. However, the system may determine that the 5 units (i.e., the submitted quantity) may all match with a resting order at a value of 4. Thus, the system concludes that the trade value (i.e., the match or execution value) is 4. It should be appreciated that the trade value may be the same as or “better than” (lower if buy order, higher if sell order) the submitted value.

PO and ABV messages may be published to data recipient computing systems via data feeds 512 and 514 as discussed in reference to FIG. 5. In scenarios that cause the generation of both PO and ABV messages, the respective messages would be published to data recipient computing systems via both data feeds 512 and 514. In one embodiment, a client computer may decide whether to subscribe to data feed 512, 514, or both.

FIGS. 6A and 6B illustrate example ABV and PO messages 600 and 610, respectively. As illustrated in example ABV and PO messages 600 and 610, ABV or aggregated by value messages and PO or per order messages implemented by an exchange computing system may both be considered to report on, or provide a view of, the positions for a financial product. For example, ABV message 600 and PO message 610 both provide data regarding a financial product CLH6. The data provided in the two messages is different, but related. In some cases, the two messages may be caused by the same event. Or, the messages may be caused by different events. When ABV and PO messages are generated by the same events, the information may be considered to overlap. For example, an event that creates multiple order updates may affect both the ABV book object and the PO book object stored in the exchange computing system memory. In one embodiment, the data generation module of an exchange computing system generates a message (e.g., ABV or PO message) whenever the order book module reports or detects an update to a book object.

As can be seen in FIGS. 6A and 6B, some of the fields in the two messages may contain the same, or redundant, information.

In one embodiment, the header fields may always be the same size, e.g., 24 bytes, regardless of whether the message is an ABV message or a PO message. This is because the header fields 602 and 612 may be considered to contain information used to route and packet the information. In contract, the body portions 604 and 614 may be considered to include substantive order or value related information. However, even certain fields within body portions 604 and 614 may overlap, which may occur if the same events caused the generation of both ABV and PO messages. For example, the Value, Sequence Number, and Side fields within body portions 604 and 614 may contain the same information. The Quantity field in body portion 604 and Order Quantity field in body portion 614 may be related, but not identical, because in an ABV message, an order for a quantity of 10 may be aggregated with other existing orders. Said another way, if orders for a value already exist on the books, and an order for quantity is added, the ABV Quantity field will be higher than the PO Order Quantity field.

FIG. 7 illustrates an example data transaction processing system 700 including primary order book object 702 and data generator 704. The order book object 702 in one embodiment represents the state of an electronic marketplace for a financial instrument. Due to regular trading activity (e.g., match events, order modifications or cancellations), the state of the order book object 702 is continually changing. Data generator 704 generates data that represents these changes to primary book object 702. In one embodiment, a transaction processor 703 performs transactions that cause a modification to the state of the order book object 702. The transaction processor 703, the order book object 702, or both, may be in communication with the data generator 704. Data generator 704 transmits the incremental changes to a data recipient computing system 706 via incremental data feed 708.

The data recipient computing system 706 includes locally maintained data recipient computing system book object 710. The data recipient computing system 706 applies information received via incremental data feed 708 to the order book object 710. Thus, as long as book object 702 is being updated/refreshed with new information, book object 710 will lag behind book object 702. If book object 702 remains static, book object 710 may catch up to book object 702 so that book object 710 is an identical copy of book object 702. If book object 710 is modified at time t=t₀, but receives no more modifications, and the received modifications require 3 seconds to be transmitted and applied to book object 710, then book object 710 at time t=t₀ plus 3 seconds will have the same state as book object 702 at time t=t₀.

The exchange computing system provides disaster recovery functionality, in case a data recipient computing system experiences an outage or loses or damages its copy of the order book object. The exchange computing system includes a snapshot adaptor 712 that generates a snapshot which can be used by a data recipient computing system to recover its local copy of the book object. The snapshot may include ABV data as well as PO data. The snapshot may also include statistics about the corresponding data object, such as an order book object. If the data transaction processing system is implemented as an exchange computing system, and the snapshot is a snapshot of an order book, the statistics may comprise the highest and lowest prices, the opening price, and overall volume trade for any given day for the corresponding financial instrument or product, as well as a current market status (e.g., open, halt, closed, etc.).

In one embodiment, each data packet in the incremental data feed 708 includes a unique sequence number. That sequence number is included in the snapshot that is generated and transmitted to the data recipient computing system 706 over feed 714. The data recipient computing system 706 uses the unique sequence number associated with each data packet to recover and rebuild the data recipient computing system book object 710 if needed. For example, the data recipient computing system also receives the feed 708, which is the same feed/data that is received by the snapshot adaptor to update the instrument caches. The data recipient computing system synchronizes sequence numbers in feed 708 with sequence numbers in the encoded instrument caches received over feed 714 to rebuild order book 710. For more details on a market data recovery process implementing a snapshot, see U.S. Pat. No. 8,108,289, entitled “Market Data Recovery,” the entire disclosure of which is incorporated by reference herein and relied upon.

Just like data recipient computing system 706 uses feed 708 data to update book object 710, the exchange computing system uses feed 708 data to update the snapshot created by snapshot adaptor 712. The exchange computing system encodes the snapshot and transmits a continuous, repeating loop of the encoded snapshot to data recipient computing systems via snapshot feed 714.

In one embodiment, portions of the encoded snapshot (i.e., portions associated with instruments) are updated as other portions of the encoded snapshot are cyclically published. For example, outdated portions of the encoded snapshot, associated with one or more instruments, may be replaced with newly encoded data for those instruments. In one embodiment, the entire encoded snapshot is replaced with a new encoded snapshot as the new encoded snapshot is encoded. It should be appreciated that the transmission buffer may include more records than are stored in all of the instrument caches. Newly received data is received by the snapshot adaptor and used to update the instrument cache. The newly updated instrument cache data is placed into the transmission buffer. Older data, for other instrument cache, also remains in the transmission buffer. Thus, the transmission buffer, in one embodiment, contains data for a variety of different instruments, which have been encoded at different times depending on the encoding intervals associated with the different instruments.

Accordingly, the snapshot adaptor updates the snapshot with newly received incremental market feed data, encodes the snapshot, and publishes the snapshot to data recipient computing systems via the continuously looped snapshot feed 714. The snapshot feed 714 is replaced with new information/data as new incremental data is received via feed 708.

Data feeds are typically configured to send a message type that can be deconstructed and/or interpreted by the recipient, e.g., a trader's computer that connects to an exchange computing system. The message structure is organized and structured according to the information contained therein, and the structures/computing systems receiving the message have to be configured to recognize and decipher the message. For example, the data feed 708 may include both ABV data as well as PO data, as described in U.S. patent application Ser. No. 15/155,565, filed on May 16, 2016, entitled “Systems and Methods for Consolidating Multiple Feed Data”, the entire disclosure of which is incorporated by reference herein and relied upon.

A snapshot adaptor, such as one implemented by the CME, may include an encoding system which determines whether outbound messages can and should be generated in the disclosed consolidated data structure format. An exchange computing system may generate messages in response to events, as discussed herein. The messages may be indicative of the state of an environment. Or, the messages may be indicative of changes to be made to the state of an environment.

As discussed above, the data transaction processing system processes incoming electronic data transaction request messages, and generates responsive electronic data transaction result messages. Some request messages may cause the generation of many result messages.

For clarity, the snapshot adaptor may be configured to encode instruments upon the end of an event. This way, the data recipient computing systems only receive fully completed events. The messages received by the data recipient computing system are accordingly guaranteed to be part of a completed event. An event may be a fill event that includes many trades that are triggered from a single incoming message.

Each message in stream 708 may mark whether that message represents the end of an event. Each message may accordingly include an “End of Event” field. For example, an incoming message may cause the generation of 45 new outbound messages. The data transaction processing system may logically group those 45 messages together as part of a single event. Only the last message from the 45 messages may indicate that the message is associated with an End of Event.

To facilitate the recovery process, the exchange computing system may also include a sequence number with each data packet that is transmitted in the data feed 708. Those sequence numbers are also included in the encoded data that is transmitted out to data recipient computing systems over feed 714. If a customer needs to rebuild/recover data recipient computing system book object 710, the sequence numbers are used to synchronize feed 708 (which includes the sequence numbers) with snapshot feed data 714 (which also includes the sequence numbers).

Table 1 below gives an example of type of information that may be includes in incremental data feed 708.

TABLE 1 Instrument ID End of Event Sequence Number 1 No 101 2 Yes 102 3 No 103 4 Yes 104 5 No 105 2 Yes 106 3 Yes 107

Incremental data messages include instrument IDs identifying the particular instruments that have been updated in the primary book object 702, whether or not a message marks the end of an event, and the sequence number for that message, or the data packet containing the message, which can be used to rebuild the book object at the data recipient computing system if needed. The sequence number indicates the order of those messages in the incremental data feed.

FIG. 8 illustrates an example block diagram for example snapshot adaptor 712. The snapshot adaptor includes an instrument cache 802, which maintains a current state of each instrument. As new/incremental updates for various instruments are received by the snapshot adaptor, the updates are immediately applied to the respective instrument caches. The snapshot adaptor also includes an encoding system 804, which encodes cached data in a format expected by the data recipient computing systems.

In one embodiment, the encoding system 804 may encode the cache 802 data into a binary data array. In one embodiment, the encoding system 804 may encode the cache 802 data into a SBE (Simple Binary Encoding) format, which is a protocol supporting applications requiring low-latency, such as those implemented by exchange computing systems and traders (e.g., data recipient computing systems that engage in financial trading). SBE may allow for variable length fields at the end of a repeating group or message. SBE may also impose several other restrictions in return for more than an order of magnitude increase in throughput at very low and predictable latency. The encoding performed by the encoding system 804 may, in some instances, be the most computationally expensive step in the snapshot adaptor/object recovery processes. Encoding may involve compressing and/or arranging the incoming data (via feed 708) into a specific arrangement and format that is restrictive in order to optimize throughput and minimize latency (for the data transmitted over feed 714).

Referring now to FIG. 11, experimental plot 1100 illustrates relative times required to perform various tasks by the snapshot adaptor. The snapshot adaptor performs various tasks, including receiving data, updating an instrument cache, encoding an instrument cache, and publishing the encoded instrument cache. Example computer codes for these tasks are shown as item 1102, which indicates that plot 1100 includes the 50^(th) percentile of the various task processing times. Experimental data for a snapshot adaptor as it performed these tasks was collected over a 30 minute period, 08:30 to 09:00, as indicated by the x-axis of plot 1100. The y-axis of plot 1100 is the amount of time required to perform the different tasks. Item 1104 indicates the amount of time, in nanoseconds, required to encode the various messages/instrument caches. For clarity, the dashed circle highlights the experimental data associated only with the encoding process, e.g., the dashed circle is associated with item 1104. Item 1106 indicates the amount of time, in nanoseconds, required to perform other non-encoding tasks. As shown in FIG. 11, the encoding process dominates the overall time of all of the other tasks performed by the snapshot adaptor. In other words, the snapshot adaptor's encode process is the most computationally expensive task performed by the snapshot adaptor, as supported by actual experimental data extracted from the data transaction processing system.

Referring back to FIG. 9, as different instrument caches are encoded upon their respective encoding conditions/encoding intervals and via their respective encoding processes, the encoding system writes the newly encoded data to the transmission buffer. Thus, each time that the encoding system encodes data, the encoding system must control at least a portion of the transmission buffer, to be able to write into that specific portion of the transmission buffer. At the same time, the publish process, implementing the iterator, publishes other portions of the transmission buffer, not the portions currently being updated by the encoding system, to data recipient computing systems. Accordingly, the encode process may be writing to the transmission buffer when the publish process attempts to read that same portion, resulting in a lockout or a halting of the encode and/or publish process. The disclosed encoding system accordingly minimizes, in one embodiment, contention for the transmission buffer between the encode process and the publish process, thus reducing publishing delays that may arise from such contention, by eliminating unnecessary or undesirable encoding cycles.

Because of the computational expense of encoding the instrument data, the encoding system 804 may determine when to encode such data so as to minimize encoding and transmission cycles, without delaying the transmission of received data. Moreover, the encoding system 804 may only encode cached data at the end of an event. For example, the encoding system 804 may be configured according to specific rules to optimize the amount of time between encoding sessions for the various instruments.

Snapshot adaptor 712 may also include a transmission buffer 806, which holds encoded data until it is to be published/transmitted via feed 714 to data recipient computing systems. It should be appreciated that the rate of publishing of data from the transmission buffer depends on the bandwidth/publishing rate associated with feed 714. Because of the size of the amount of data that needs to be transmitted, the contents of the transmission buffer may be published over feed 714 over several cycles. Moreover, the snapshot adaptor may continue to publish the connects of the transmission buffer repeatedly or cyclically, e.g., in a repeating loop, until the encoding system encodes/prepares new data.

The instrument cache data may be in a first format, and the transmission buffer data may be in a different format resulting from the encoding process. One of ordinary skill would understand that formatting change or encoding of data may be performed for a variety of reasons, including optimizing the data for later transmission, or for preparing the data to be in a format expected by the data recipient computing system.

The snapshot adaptor may additionally or alternatively include iterator 808 for reporting or indicating (e.g., to the encoding system 804) the most recently published packet of data from the transmission buffer. The iterator 808 repeatedly cycles through the contents of the transmission buffer to indicate the location of the transmission buffer that is currently being published, or was most recently published. The snapshot adaptor may additionally or alternatively include a timer 810 for determining the amount of time needed to publish all of the contents of the transmission buffer one time. Thus, iterator 808 reports on the location in the transmission buffer being cyclically transmitted, and timer 810 reports on how long is needed to publish the full contents of the transmission buffer one time. The timer 810 may periodically store such timing information in memory.

FIG. 9 illustrates example processes executed by the snapshot adaptor 712. The snapshot adaptor may be configured to run several process in parallel. The parallel processes may be completely independent of each other, or they may be related (e.g., the output of one process may feed into another process). The processes may start and stop at different times. Each process may be implemented as a separate processing thread, where one processing thread is triggered by another processing thread.

For example, the instrument cache for each of the instruments may be continually updated as incremental data is received via process 902. Snapshot adaptor maintains separate caches for each instrument associated with the incremental data feed/data generator. As new incremental data is received (e.g., example data contained in Table 1 above) by the snapshot adaptor, process 902 updates the cache for that instrument with the new data. For example, instrument cache 802 may include Instrument 1 Cache 906, Instrument 2 Cache 908, and Instrument 3 Cache 910. The encoding system 804 determines when to initiate encode process 912A, B or C. In particular, the encoding system 804 determines when to initiate encode process 912A to encode Instrument 1 Cache 906, when to initiate encode process 912B to encode Instrument 2 Cache 908, and when to initiate encode process 912C to encode Instrument 3 Cache 910. In one embodiment, the encoding system may use the same encode process to encode any one of the instrument caches.

The encoding system in one embodiment may be configured to optimally balance between encoding data immediately as it is received and applied to the instrument cache, and waiting until the previously encoded data (in the transmission buffer) has been transmitted to the data recipient computing system over snapshot feed 714. Again, because encoding may a computationally process, the snapshot adaptor may conserve resources by encoding data when it can be optimally transmitted. The size and contents of the transmission buffer however may be constantly fluctuating. The type of incremental data may include every change made to every instrument. Thus, the incremental data may not be aggregated, e.g., at a price level. As discussed above, MBO/PO messages may carry much more data than MBP/ABV messages because MBO/PO messages reflect information about each order, whereas MBP/ABV messages contain information about orders affecting some predetermined value levels. If the exchange computing system data generator publishes PO data, the size of the transmission buffer can quickly fluctuate, which in turn may affect the optimum encoding interval to encode an instrument.

The encoded data is placed in the transmission buffer 806, which is represented as transmission buffer 914 in FIG. 9. As shown in FIG. 9, the transmission buffer 914 includes encoded data to be published for multiple instruments 916, 918, and 920. Encoded instrument 916, encoded via encode process 912A, may correspond to instrument 1 cache 906, encoded instrument 918, encoded via encode process 912B, may correspond to instrument 2 cache 908, and encoded instrument 920, encoded via encode process 912C, may correspond to instrument 3 cache 910. Each encoded instrument may include a number of records, which may fluctuate depending on the data received via feed 708. For example, encoded instrument 916 includes records 922 and 924, encoded instrument 918 includes records 926, 928 and 930, and encoded instrument 920 includes records 932 and 934. Each record may be a byte array corresponding to an encoding protocol, e.g., Simple Binary Encoding.

As the match engine processes orders for the different instrument, each order may, in one embodiment, result in one record change in the transmission buffer. Thus, the size of the transmission buffer may vary dramatically as different orders are affected/impacted by different transaction processor/match engine activity, and these impacts are reflected in the incremental market data feed. Contents of the transmission buffer 914 are published over the feed 714 at a rate (e.g., bytes/second) associated with feed 714.

The snapshot adaptor may accordingly include the ability to determine the current sizes of the various instrument caches as well as the sizes of the various encoded instrument data within the transmission buffer. The snapshot adaptor may periodically determine and store such sizing information in a memory coupled to the transmission buffer. The sizes may be calculated in terms of how much memory is required to store the information, how many records make up the instrument caches, or many instruments make up the instrument cache, etc.

Thus, the snapshot adaptor receives data for multiple instruments. The incoming data may be interleaved, each data for different instruments may be mixed together, e.g., Table 1 above where data for instrument ID 2 is interweaved with and separated by data for other instruments. Data that is published out of the transmission buffer is grouped relative to the instruments. In other words, snapshot adaptor publishes all the encoded data 916 for instrument 1 before publishing the encoded data 918 for instrument 2. Thus, the iterator iterates through the contents of the transmission buffer sequentially.

In one embodiment, encoded instrument cache data for a given instrument may be added to the same reference point or location in the transmission buffer. For instance, encoded data for instrument cache 906 is added to 916 data. Encoded data for instrument cache 908 is added to 918 data. Thus, the order in which encoded data is published remains the same.

The iterator 808 may be implemented as iterator 936, which in one implementation may be a pointer that cyclically keeps track of and reports the current transmission point/last transmitted packet of the transmission buffer. In the example of FIG. 9, the iterator 936 reports (e.g., to encoding system 804 configured to run encode process 912A, B and/or C) that encoded data 920 (encoded via encode process 912C) is now about to be published. As shown by the cyclical loop drawn in dashed lines in FIG. 9, snapshot adaptor will publish the contents of the transmission buffer in a cyclical repeating loop. As new data is encoded, some or all of the contents of the transmission buffer 914 will be replaced with newly encoded data, at a time determined by the encoding system 804.

Thus, encoding an instrument cache and adding the encoded instrument cache to the transmission buffer may, in one embodiment, be considered to be queuing the encoded instrument cache to be published. Contents added to the transmission buffer are not published upon addition to the transmission buffer. Instead, the newly added contents must wait in the transmission buffer until it is their turn to be published, i.e., until the iterator tracking the cyclical, sequential publishing points to the newly added contents.

The snapshot adaptor applies the incremental updates upon receipt to the instrument cache. Accordingly, the size of the instrument cache for any one instrument is dependent upon the number of updates received for that instrument. As noted above, encoding the instrument cache for an instrument may involve transformation of the data in the instrument cache. For example, the transformation may include modifying the format of the data, e.g., the instrument cache data may be encoded or transformed into Simple Binary Encoding format. The encoding system 804 runs a process to transform the data into a format appropriate or optimized for transmission. In one embodiment, encoding process may be computationally expensive, e.g., the encoding process 912 may be a bottleneck in the processes performed by the snapshot adaptor. Encoding process 912 may refer to one or more of 912A, 912B or 912C.

The amount of time needed to encode the instrument cache data depends on the size of the instrument cache. Once encoded, the publish process cyclically publishes the encoded data over feed 714. The amount of time required to publish data from the transmission buffer depends on the amount of data held by the transmission buffer, and the publish rate of transmission buffer over feed 714. The rate of publishing the data depends on the capacity and configuration of the feed 714. Accordingly, the snapshot adaptor should be understood to be a grouping of related, but separate, systems or processes that transform and publish data.

The encoding system 804 in one embodiment is configured to encode instrument cache data such that the encoded data will be published upon completion of the encoding process. In other words, even if the size of the instrument cache and the transmission buffer contents may be varying, the encoding system starts encoding instrument cache data such that when the instrument cache data encoding is completed for a given instrument, the publish process completes the instrument just prior to the given instrument and can thus immediately publish the newly encoded data.

The encoding system in one embodiment determines an encoding interval for each instrument, and encodes the instrument cache for a particular instrument according to the encoding interval for that instrument. After encoding an instrument cache, the encoding system may reset, e.g., to zero, the encoding interval for an instrument cache.

The encoding system may calculate the encoding interval for an instrument based on the contents of the transmission buffer. For example, referring back to FIG. 9, the data feed 708 may include information/updates for instrument 2, which is applied to instrument 2 cache 908. Cache 908 is encoded, via encode process 912B, according to an encoding interval for instrument 2. The size and contents of transmission buffer 914 affects the encoding interval for instrument 2. The publish process 904 publishes the contents of the transmission buffer in order, and the iterator 936 keeps track of what is currently being published. As the contents of transmission buffer 914 are published over feed 714, iterator 936 traverses over transmission buffer and shifts to reflect the publishing point. In FIG. 9, the publish process has just finished publishing encoded instrument 918 corresponding to instrument 2 and instrument 2 cache 908. The iterator 936 is accordingly illustrated as beginning to publish information related to encoded instrument 920. The contents of 918 will not be published again until everything else in the transmission buffer, namely 920 and 916, has been published. The time needed to publish 920 and 916 depends on the size of 920 and 916, as well as the transmission rate over 714.

In one embodiment, the transmission rate over 714 may be static, or may not substantially vary. Thus, the major factor for changes in publishing times for any one instrument, e.g., 916 or 920, may be the size, e.g., the number of records 922, 924, etc., of 916 and 920. The encoding system accordingly determines, or estimates, how much time will be needed to publish 920 and 916 based on their size. For example, the timer 810 may be used to determine the times needs to encode and/or publish the various instruments.

The encoding system may assign a preconfigured value for each record to be published, and multiply that preconfigured value with the number of collective records in the instruments other than the instrument for which the encoding interval is being determined. For example, the operator of the exchange computing system may have assigned a preconfigured per record value of 3 microseconds. Thus, the encoding system may multiply 3 microseconds times four (for four records 932, 934, 922 and 924) resulting in 12 microseconds. The encoding system may accordingly store 12 microseconds as the publishing time associated with 920 and 916.

The encoding system may also determine or estimate the amount of time needed to actually encode each of the instrument caches. The amount of time needed to encode an instrument cache may depend on the size of that instrument cache. The encoding system may again use a preconfigured value and multiply it times the size of an instrument cache to determine how much time is needed to encode an instrument cache. For instance, based on the size of instrument 2 cache 908, the encoding system may determine that 4 microseconds are needed to encode instrument 2 cache 908. The encoding system then subtracts the amount of time needed to encode instrument 2 cache 908 from the amount of time needed to encode 916 and 920, namely, 12 microseconds minus 4 microseconds, resulting in 8 microseconds. The encoding system sets the encoding interval for instrument 2 cache 908 to 8 microseconds. The instrument cache update process may receive and update 50 updates/changes associated with instrument 2 in just 2 or 3 microseconds, but the encoding system encodes instrument 2 cache 908 every 8 microseconds. Thus, the encoding system ensures that instrument 2 cache 908 encoding ends right at, or substantially close to, the time that publish process 904 is ready to publish instrument 2 data 918. In other words, the encoding system completes encoding instrument 2 cache 908 when iterator 936 finishes iterating through the instrument data in the transmission buffer right before 918.

It should be appreciated that once an encode process begins for an instrument cache, new updates received for that instrument cache may be stored in a buffer or queue until the encoding system has completed encoding the instrument cache. Moreover, it should be also appreciated that instrument data in the transmission buffer for any one instrument cannot be replaced while that same instrument is being published. In other words, if the iterator indicates that some portion of instrument 1 data 916 is being published, the encode process 912A (which encodes Instrument 1 Cache 906) cannot write new data to any of records 922 or 924.

In one embodiment, instead of preconfigured values for the amount of time needed to encode an instrument cache, and the amount of time needed to publish encoded data, the encoding system may calculate the times needed to encode instrument caches and to publish encoded instruments based on previous/historical encode and publish data.

The snapshot adaptor may also determine and store historical, or statistical, information associated with encoding and/or publishing instrument caches. The snapshot adaptor may track the amount of time needed to perform these actions for previous instrument caches, and use such information when calculating an encoding interval for an instrument.

Regardless, the encoding system calculates an encoding interval for each instrument as the size of the instrument cache and/or the transmission buffer fluctuates. If the transmission buffer grows larger, the encoding interval may become longer for each instrument. If the instrument cache for an instrument grows, the encoding interval may become smaller for that instrument. However, the encoding interval may change in either direction (e.g., become longer or shorter), or stay the same, depending on how the instrument cache size and the transmission buffer size fluctuates.

Thus, the encoding interval for a given, target instrument may vary inversely with the size of that target instrument's cache. And, the encoding interval for the target instrument may vary linearly with the amount of data in the transmission buffer for instruments other than the target instrument.

In one embodiment, the encoding interval for a given, target instrument may be inversely proportional to the size of that target instrument's cache. And, the encoding interval for the target instrument may be directly proportional to the amount of data in the transmission buffer for instruments other than the target instrument.

It should thus be appreciated that the encoding interval for a given instrument A may depend on one or both of (i) the time needed to encode A, which depends on A's size (e.g., number of updates received for A via the incremental data feed) or (ii) the time needed to publish all encoded instrument data in the transmission buffer other than data for instrument A, which in turn depends on the size of encoded instrument data in the transmission buffer other than data for instrument A (e.g., which may be based on the number of updates received for instruments other than A via the incremental data feed).

In one embodiment, the encoding interval may be determined based on the number of instruments in the instrument cache and the number of instruments in the transmission buffer. For example, the snapshot adaptor may receive updates for three instruments. The transmission buffer may contain data for eight instruments. A preconfigured ratio may be set to be 50%, meaning that when the ratio of instrument caches to instruments in the transmission buffer becomes 50%, all the instrument caches should be encoded. Upon receiving updates for one more instrument (i.e., a fourth instrument), the encoding system determines that the 50% ratio (4 instrument caches to 8 instruments in the transmission buffer) has been reached, and encodes the four instrument caches.

In one embodiment, the encoding system may simply be configured to encode all instrument caches when the number of instrument caches exceeds a preconfigured amount.

In one embodiment, contents of the incoming incremental updates data stream may be evaluated to determine whether data should be encoded at all. For example, after encoding the instrument caches at time t=t₀, if the snapshot adaptor does not receive any new changes or updates, then the encoding system does not encode the instrument caches. In other words, if the instrument caches have not been updated or changed in any way since last being encoded, then the encoding system does not encode the instrument caches again.

In one embodiment, the incoming incremental updates data stream indicates whether a message (or data packet associated with a sequence number, as shown in Table 1) marks the end of a logical event. The encoding system may only check whether an encoding interval has elapsed, or if the instrument cache should be encoded, if the most recently received message marked the end of an event. In other words, the encoding system does not encode an instrument cache that is in the middle of receiving updates for a not yet complete event.

FIG. 10 illustrates an example state diagram 1000 for an instrument cache as it is updated with new data and encoded for publishing. As different processes are performed on data associated with an instrument cache, the instrument cache state is modified. The instrument cache for any one given instrument may be at an initial state 1002. When newly received data is applied to the instrument cache, e.g., the instrument cache is updated with the new data. The state of the instrument cache may be considered to be modified to an updated instrument cache state 1004. After the instrument cache, in state 1004, is encoded after the occurrence of an encoding condition, the state of the instrument cache may be state 1006. The encoded instrument cache in state 1006 is then published to data recipient computing systems.

FIG. 12 illustrates an illustrates an example process 700 indicating an example method of implementing the disclosed exchange computing system, as may be implemented with computer devices and computer networks, such as those described with respect to FIGS. 1 and 2. Embodiments may involve all, more or fewer actions indicated by the blocks of FIG. 12. The actions may be performed in the order or sequence shown or in a different sequence.

Process 1200 begins with receiving, by a first processor, data for a plurality of instrument caches including a first instrument cache, as shown in block 1202. Process 1200 includes updating, by the first processor, the plurality of instrument caches based on the received data, as shown in block 1204. Process 1220 includes, upon each occurrence of an encoding condition associated with the first instrument cache, encoding, by the first processor, the updated first instrument cache, as shown in block 1206. In one embodiment, the process may include detecting the occurrence of an encoding condition associated with the first instrument cache. Process 1200 also includes queuing, by the first processor, the encoded first instrument cache for publishing, as shown in block 1208. Process 1200 may additionally include publishing a plurality of encoded instrument caches including the encoded first instrument cache in a sequential repeating loop. For example, all of the encoded instrument cache data may be stored in a transmission buffer that is continuously published. For example, an iterator may keep track of which portion of the transmission buffer is currently being published.

In one embodiment, the encoding condition associated with the first instrument cache is an elapse of an encoding interval associated with the first instrument cache.

Process 1200 may additionally include determining the encoding interval associated with the first instrument cache by subtracting (i) the amount time needed to encode the updated first instrument cache from (ii) the amount of time needed to publish previously encoded instrument caches other than a previously encoded first instrument cache in a transmission buffer. In one embodiment, (i) depends upon a size of the updated first instrument cache, and wherein (ii) depends upon sizes of the previously encoded instrument caches other than the previously encoded first instrument cache in the transmission buffer. These sizes may dynamically fluctuate. Accordingly, the encoding interval for an instrument cache may dynamically fluctuate. The size of the updated first instrument cache may greater than a size of the first instrument cache before being updated with the received data. In other words, the size of an instrument cache may increase upon being updated with received data. The instrument cache for an instrument may be erased after the updated instrument cache is encoded. Process 1200 may additionally include calculating (i) based upon historical data associated with encoding instrument caches; and calculating (ii) based upon historical data associated with publishing encoded instrument caches.

Process 1200 may additionally include resetting the encoding interval associated with the first instrument cache upon completing encoding of the updated first instrument cache. The encoding system may be in communication with a timer that keeps track for how much time has elapsed since the last time an instrument cache was encoded. The timer associated with an instrument cache may accordingly be reset upon encoding an instrument cache.

Process 1200 may additionally include receiving, by a second processor, the data received by the first processor and the encoded first instrument cache; determining, by the second processor, at least one same sequence number from each of the received data and the encoded first instrument cache; rebuilding, by the second processor, the second data object based on the received data, the encoded first instrument cache, and the at least one same sequence number. For example, a data recipient computing system may rebuild its copy of an order book based on the incremental data feed and the snapshot adaptor's encoded feed.

Process 1200 may additionally include receiving data for a second instrument cache; updating the second instrument cache based on the received second instrument cache data; upon an elapse of an encoding interval associated with the second instrument cache, encoding the updated second instrument cache; and queuing the encoded second instrument cache for publishing. The snapshot adaptor may accordingly receive, update, and encode different instrument cache data at different times.

In one embodiment, process 1200 includes receiving first data for a first instrument cache; updating the first instrument cache based on the first received data; receiving second data for a second instrument cache; updating the second instrument cache based on the second received data; upon an occurrence of an encoding condition associated with the first instrument cache, encoding the updated first instrument cache to generate a first encoded first instrument cache; upon an occurrence of an encoding condition associated with the second instrument cache, encoding the updated second instrument cache to generate a first encoded second instrument cache; publishing the first encoded first instrument cache and the first encoded second instrument cache in a sequential repeating loop; receiving third data for the first instrument cache; updating the first instrument cache based on the third received data; upon an occurrence of the encoding condition associated with the first instrument cache, encoding the updated first instrument cache to generate a second encoded first instrument cache; and publishing the second encoded first instrument cache and the first encoded second instrument cache in a sequential repeating loop.

Referring back to FIG. 1, the trading network environment shown in FIG. 1 includes exemplary computer devices 114, 116, 118, 120 and 122 which depict different exemplary methods or media by which a computer device may be coupled with the exchange computer system 100 or by which a user may communicate, e.g., send and receive, trade or other information therewith. It should be appreciated that the types of computer devices deployed by traders and the methods and media by which they communicate with the exchange computer system 100 is implementation dependent and may vary and that not all of the depicted computer devices and/or means/media of communication may be used and that other computer devices and/or means/media of communications, now available or later developed may be used. Each computer device, which may comprise a computer 200 described in more detail with respect to FIG. 2, may include a central processor, specifically configured or otherwise, that controls the overall operation of the computer and a system bus that connects the central processor to one or more conventional components, such as a network card or modem. Each computer device may also include a variety of interface units and drives for reading and writing data or files and communicating with other computer devices and with the exchange computer system 100. Depending on the type of computer device, a user can interact with the computer with a keyboard, pointing device, microphone, pen device or other input device now available or later developed.

An exemplary computer device 114 is shown directly connected to exchange computer system 100, such as via a T1 line, a common local area network (LAN) or other wired and/or wireless medium for connecting computer devices, such as the network 220 shown in FIG. 2 and described with respect thereto. The exemplary computer device 114 is further shown connected to a radio 132. The user of radio 132, which may include a cellular telephone, smart phone, or other wireless proprietary and/or non-proprietary device, may be a trader or exchange employee. The radio user may transmit orders or other information to the exemplary computer device 114 or a user thereof. The user of the exemplary computer device 114, or the exemplary computer device 114 alone and/or autonomously, may then transmit the trade or other information to the exchange computer system 100.

Exemplary computer devices 116 and 118 are coupled with a local area network (“LAN”) 124 which may be configured in one or more of the well-known LAN topologies, e.g., star, daisy chain, etc., and may use a variety of different protocols, such as Ethernet, TCP/IP, etc. The exemplary computer devices 116 and 118 may communicate with each other and with other computer and other devices which are coupled with the LAN 124. Computer and other devices may be coupled with the LAN 124 via twisted pair wires, coaxial cable, fiber optics or other wired or wireless media. As shown in FIG. 1, an exemplary wireless personal digital assistant device (“PDA”) 122, such as a mobile telephone, tablet based compute device, or other wireless device, may communicate with the LAN 124 and/or the Internet 126 via radio waves, such as via WiFi, Bluetooth and/or a cellular telephone based data communications protocol. PDA 122 may also communicate with exchange computer system 100 via a conventional wireless hub 128.

FIG. 1 also shows the LAN 124 coupled with a wide area network (“WAN”) 126 which may be comprised of one or more public or private wired or wireless networks. In one embodiment, the WAN 126 includes the Internet 126. The LAN 124 may include a router to connect LAN 124 to the Internet 126. Exemplary computer device 120 is shown coupled directly to the Internet 126, such as via a modem, DSL line, satellite dish or any other device for connecting a computer device to the Internet 126 via a service provider therefore as is known. LAN 124 and/or WAN 126 may be the same as the network 220 shown in FIG. 2 and described with respect thereto.

Users of the exchange computer system 100 may include one or more market makers 130 which may maintain a market by providing constant bid and offer prices for a derivative or security to the exchange computer system 100, such as via one of the exemplary computer devices depicted. The exchange computer system 100 may also exchange information with other match or trade engines, such as trade engine 138. One skilled in the art will appreciate that numerous additional computers and systems may be coupled to exchange computer system 100. Such computers and systems may include clearing, regulatory and fee systems.

The operations of computer devices and systems shown in FIG. 1 may be controlled by computer-executable instructions stored on a non-transitory computer-readable medium. For example, the exemplary computer device 116 may store computer-executable instructions for receiving order information from a user, transmitting that order information to exchange computer system 100 in electronic messages, extracting the order information from the electronic messages, executing actions relating to the messages, and/or calculating values from characteristics of the extracted order to facilitate matching orders and executing trades. In another example, the exemplary computer device 118 may include computer-executable instructions for receiving market data from exchange computer system 100 and displaying that information to a user.

Numerous additional servers, computers, handheld devices, personal digital assistants, telephones and other devices may also be connected to exchange computer system 100. Moreover, one skilled in the art will appreciate that the topology shown in FIG. 1 is merely an example and that the components shown in FIG. 1 may include other components not shown and be connected by numerous alternative topologies.

Referring back to FIG. 2, an illustrative embodiment of a general computer system 200 is shown. The computer system 200 can include a set of instructions that can be executed to cause the computer system 200 to perform any one or more of the methods or computer based functions disclosed herein. The computer system 200 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices. Any of the components discussed above, such as the processor 202, may be a computer system 200 or a component in the computer system 200. The computer system 200 may be specifically configured to implement a match engine, margin processing, payment or clearing function on behalf of an exchange, such as the Chicago Mercantile Exchange, of which the disclosed embodiments are a component thereof.

In a networked deployment, the computer system 200 may operate in the capacity of a server or as a client user computer in a client-server user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 200 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 200 can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 200 is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

As illustrated in FIG. 2, the computer system 200 may include a processor 202, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 202 may be a component in a variety of systems. For example, the processor 202 may be part of a standard personal computer or a workstation. The processor 202 may be one or more general processors, digital signal processors, specifically configured processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data. The processor 202 may implement a software program, such as code generated manually (i.e., programmed).

The computer system 200 may include a memory 204 that can communicate via a bus 208. The memory 204 may be a main memory, a static memory, or a dynamic memory. The memory 204 may include, but is not limited to, computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one embodiment, the memory 204 includes a cache or random access memory for the processor 202. In alternative embodiments, the memory 204 is separate from the processor 202, such as a cache memory of a processor, the system memory, or other memory. The memory 204 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data. The memory 204 is operable to store instructions executable by the processor 202. The functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 202 executing the instructions 212 stored in the memory 204. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.

As shown, the computer system 200 may further include a display unit 214, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display 214 may act as an interface for the user to see the functioning of the processor 202, or specifically as an interface with the software stored in the memory 204 or in the drive unit 206.

Additionally, the computer system 200 may include an input device 216 configured to allow a user to interact with any of the components of system 200. The input device 216 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the system 200.

In a particular embodiment, as depicted in FIG. 2, the computer system 200 may also include a disk or optical drive unit 206. The disk drive unit 206 may include a computer-readable medium 210 in which one or more sets of instructions 212, e.g., software, can be embedded. Further, the instructions 212 may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions 212 may reside completely, or at least partially, within the memory 204 and/or within the processor 202 during execution by the computer system 200. The memory 204 and the processor 202 also may include computer-readable media as discussed above.

The present disclosure contemplates a computer-readable medium that includes instructions 212 or receives and executes instructions 212 responsive to a propagated signal, so that a device connected to a network 220 can communicate voice, video, audio, images or any other data over the network 220. Further, the instructions 212 may be transmitted or received over the network 220 via a communication interface 218. The communication interface 218 may be a part of the processor 202 or may be a separate component. The communication interface 218 may be created in software or may be a physical connection in hardware. The communication interface 218 is configured to connect with a network 220, external media, the display 214, or any other components in system 200, or combinations thereof. The connection with the network 220 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly. Likewise, the additional connections with other components of the system 200 may be physical connections or may be established wirelessly.

The network 220 may include wired networks, wireless networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, or WiMax network. Further, the network 220 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to, TCP/IP based networking protocols.

Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.

In an alternative embodiment, dedicated or otherwise specifically configured hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems. One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.

In accordance with various embodiments of the present disclosure, the methods described herein may be implemented by software programs executable by a computer system. Further, in an exemplary, non-limited embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement one or more of the methods or functionality as described herein.

Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP, HTTPS) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed herein are considered equivalents thereof.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and anyone or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a device having a display, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. Feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in any form, including acoustic, speech, or tactile input.

Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. It should be appreciated that the disclosed embodiments may be applicable to other types of messages depending upon the implementation. Further, the messages may comprise one or more data packets, datagrams or other collection of data formatted, arranged configured and/or packaged in a particular one or more protocols, e.g., the FIX protocol, TCP/IP, Ethernet, etc., suitable for transmission via a network 214 as was described, such as the message format and/or protocols described in U.S. Pat. No. 7,831,491 and U.S. Patent Publication No. 2005/0096999 A1, both of which are incorporated by reference herein in their entireties and relied upon. Further, the disclosed message management system may be implemented using an open message standard implementation, such as FIX, FIX Binary, FIX/FAST, or by an exchange-provided API.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings and described herein in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.

It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of this invention. 

What is claimed is:
 1. A system comprising: a processor configured to: determine an interval for encoding data, received and accumulated in a memory coupled with the processor over a period of time for subsequent encoding and transmission, as a difference between an amount of time needed to encode the accumulated received data and an amount of time needed to transmit previously encoded previously accumulated data so as to maximize the amount of accumulated data that is encoded upon elapse of the interval while minimizing the time between completion of the transmission of previously encoded previously accumulated data and the commencement of a subsequent transmission; and encode, upon an elapse of the interval the accumulated received data.
 2. The system of claim 1, wherein the received data indicates one or more modifications to a data object based upon processing, by a hardware matching processor, one or more electronic data transaction request messages, each of which includes a request to perform a transaction related to a financial instrument represented by the data object
 3. The system of claim 1, wherein the received data indicates one or more modifications to a data object wherein the data object is a first data object, and wherein the received data includes at least one sequence number for rebuilding a second data object.
 4. The system of claim 1, wherein the amount of time needed to encode the received data stored in the memory depends upon a size of the received data stored in the memory, and wherein the amount of time needed to transmit previously encoded received data depends upon sizes of the previously encoded received data that has not yet been transmitted.
 5. A computer implemented method comprising: upon each occurrence of an event associated with an accumulation of data received over a period of time and stored in a memory, encoding, by a processor, the received data stored therein; and queuing, by the processor, the encoded received data for transmission.
 6. The computer implemented method of claim 5, further comprising transmitting the encoded received data in a sequential repeating loop with other encoded received data encoded upon occurrence of another event associated with the accumulation of data received over a period of time and stored in the memory.
 7. The computer implemented method of claim 5, wherein the event comprises an elapse of an interval.
 8. The computer implemented method of claim 7, further comprising determining the interval as a difference between the amount of time needed to encode the received data stored in the memory and the amount of time needed to transmit previously encoded received data from the memory.
 9. The computer implemented method of claim 8, further comprising resetting the interval upon completing encoding of the received data stored in the memory.
 10. The computer implemented method of claim 8, wherein the amount of time needed to encode the received data stored in the memory depends upon a size of the received data stored in the memory, and wherein the amount of time needed to transmit previously encoded received data depends upon sizes of the previously encoded received data that has not yet been transmitted.
 11. The computer implemented method of claim 10, wherein the size of the received data stored in the memory is greater than a size of the memory prior to receipt of the data.
 12. The computer implemented method of claim 8, further comprising: calculating the amount of time needed to encode the received data stored in the memory based upon historical data associated with previously encoding data stored in the memory; and calculating the amount of time needed to transmit previously encoded received data based upon historical data associated with transmitting previously encoded received data.
 13. The computer implemented method of claim 5, wherein encoding the received data stored in the first memory comprises using Simple Binary Encoding.
 14. The computer implemented method of claim 5, wherein the received data indicates one or more modifications to a data object.
 15. The computer implemented method of claim 14, wherein the one or more modifications to the data object are based upon processing one or more electronic data transaction request messages.
 16. The computer implemented method of claim 15, wherein each electronic data transaction request message includes a request to perform a transaction related to a financial instrument represented by the data object.
 17. The computer implemented method of claim 15, wherein the processing comprises matching performed by a hardware matching processor.
 18. The computer implemented method of claim 14, wherein the data object is a first data object, and wherein the received data includes at least one sequence number for rebuilding a second data object.
 19. The computer implemented method of claim 18, further comprising: receiving, by another processor, the received data and the encoded received data from the first memory; determining, by the other processor, at least one same sequence number from each of the received data and the encoded received data; and rebuilding, by the other processor, the second data object based on the received data, the encoded received data, and the at least one same sequence number.
 20. A computer implemented method comprising: upon a first occurrence of a first event associated with a first memory, encoding first data received and stored in the first memory prior to the first occurrence; upon an occurrence of a second event associated with a second memory, encoding second data received and stored in the second memory prior to the second occurrence, the occurrence of the second event being dynamically based on an amount of time needed to transmit the encoded first data and an amount of time needed to encode the second data; transmitting the encoded received first data and encoded received second data in a sequential repeating loop, the encoded received second data being transmitted subsequent to completion of transmission the encoded received first data; upon a second occurrence of the first event, encoding third data received and stored in the first memory prior to the second occurrence, the second occurrence of the first event being dynamically based on an amount of time needed to transmit the encoded second data and an amount of time needed to encode the third data; and transmitting the encoded received third data and the encoded received second data in a sequential repeating loop, the encoded received third data being transmitted subsequent to completion of transmission the encoded received second data. 